curl/tests/certs/EdelCurlRoot-ca.prm

extensions = x509v3
[ req ]
default_bits                    = 2048
distinguished_name              = req_DN
default_md			= sha256
string_mask			= utf8only
[ req_DN ]
countryName                     = "Country Name"
countryName_value            = NN
organizationName              = "Organization Name"
organizationName_value     = Edel Curl Arctic Illudium Research Cloud
commonName                      = "Common Name"
commonName_value              = Northern Nowhere Trust Anchor
[ x509v3 ]
basicConstraints = critical,CA:true
keyUsage        = critical,keyCertSign,cRLSign
subjectKeyIdentifier = hash
- 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`
			`[ req ]`
			`default_bits = 2048`
			`distinguished_name = req_DN`
			`default_md = sha256`
			`string_mask = utf8only`
			`[ req_DN ]`
			`countryName = "Country Name"`
			`countryName_value = NN`
			`organizationName = "Organization Name"`
			`organizationName_value = Edel Curl Arctic Illudium Research Cloud`
			`commonName = "Common Name"`
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			`commonName_value = Northern Nowhere Trust Anchor`
- 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			`[ x509v3 ]`
			`basicConstraints = critical,CA:true`
			`keyUsage = critical,keyCertSign,cRLSign`
			`subjectKeyIdentifier = hash`