curl/tests/certs/Server-localhost.nn-sv.prm

extensions = x509v3
[ x509v3 ]
subjectAltName = DNS:localhost.nn
keyUsage	= keyEncipherment,digitalSignature,keyAgreement
extendedKeyUsage = serverAuth
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid
basicConstraints = CA:false
[ req ]
default_bits                    = 1024
distinguished_name              = req_DN
default_md			= sha256
string_mask			= utf8only
[ req_DN ]
countryName                     = "Country Name is Northern Nowhere"
countryName_value            = NN
organizationName              = "Organization Name"
organizationName_value     = Edel Curl Arctic Illudium Research Cloud
commonName                      = "Common Name"
commonName_value              = localhost.nn 

[something]
# The key
# the certificate
# some dhparam
- Peter Sylvester made the HTTPS test server use specific certificates for each test, so that the test suite can now be used to actually test the verification of cert names etc. This made an error show up in the OpenSSL- specific code where it would attempt to match the CN field even if a subjectAltName exists that doesn't match. This is now fixed and verified in test 311. 2009-08-11 17:48:58 -04:00			`extensions = x509v3`
			`[ x509v3 ]`
			`subjectAltName = DNS:localhost.nn`
tests/certs: rebuild certificates with modified key usage bits The certificates were missing the digitalSignature and keyAgreement usage types, of which at least digitalSignature was checked by CyaSSL. This caused the test server in test 310 (among others) to fail the startup verification and therefore run (see http://curl.haxx.se/mail/lib-2014-07/0303.html). 2015-03-21 11:20:34 -04:00			`keyUsage = keyEncipherment,digitalSignature,keyAgreement`
- Peter Sylvester made the HTTPS test server use specific certificates for each test, so that the test suite can now be used to actually test the verification of cert names etc. This made an error show up in the OpenSSL- specific code where it would attempt to match the CN field even if a subjectAltName exists that doesn't match. This is now fixed and verified in test 311. 2009-08-11 17:48:58 -04:00			`extendedKeyUsage = serverAuth`
			`subjectKeyIdentifier = hash`
			`authorityKeyIdentifier = keyid`
tests/certs: rebuild certificates with modified key usage bits The certificates were missing the digitalSignature and keyAgreement usage types, of which at least digitalSignature was checked by CyaSSL. This caused the test server in test 310 (among others) to fail the startup verification and therefore run (see http://curl.haxx.se/mail/lib-2014-07/0303.html). 2015-03-21 11:20:34 -04:00			`basicConstraints = CA:false`
- Peter Sylvester made the HTTPS test server use specific certificates for each test, so that the test suite can now be used to actually test the verification of cert names etc. This made an error show up in the OpenSSL- specific code where it would attempt to match the CN field even if a subjectAltName exists that doesn't match. This is now fixed and verified in test 311. 2009-08-11 17:48:58 -04:00			`[ req ]`
			`default_bits = 1024`
			`distinguished_name = req_DN`
			`default_md = sha256`
			`string_mask = utf8only`
			`[ req_DN ]`
			`countryName = "Country Name is Northern Nowhere"`
			`countryName_value = NN`
			`organizationName = "Organization Name"`
			`organizationName_value = Edel Curl Arctic Illudium Research Cloud`
			`commonName = "Common Name"`
			`commonName_value = localhost.nn`

			`[something]`
			`# The key`
spelling fixes Closes #1356 2017-03-26 11:02:22 -04:00			`# the certificate`
- Peter Sylvester made the HTTPS test server use specific certificates for each test, so that the test suite can now be used to actually test the verification of cert names etc. This made an error show up in the OpenSSL- specific code where it would attempt to match the CN field even if a subjectAltName exists that doesn't match. This is now fixed and verified in test 311. 2009-08-11 17:48:58 -04:00			`# some dhparam`