esurdam/ecdsa_openssl.md

## ecdsa_openssl.md

      
    Raw
  

              ecdsa_openssl.md
            
          
    ECDSA Certs with LetsEncrypt

More on ECDSA
Info on bit length and complexity
From it you may gather that using 256 bit ECDSA key should be enough for next 10-20 years.
To view your available curves
openssl ecparam -list_curves

Now generate new private key with chosen curve (prime256v1 looks fine, like: c2pnb272w1, sect283k1, sect283r1 or secp256k1, etc). However, we will generate the key with a 384 bit prime field (secp384r1).
sudo openssl ecparam -genkey -name secp384r1 | openssl ec -out ecdsa.key -aes256

# one liner without password
openssl ecparam -genkey -name secp384r1 > ecdsa01.key

Since we are using HKPK, lets generate a pin for the key
openssl ec -in ecdsa.key -pubout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl base64

which yields the pin for my header
ZCAVPGjas9RDdNTsY9hOOnP+i0xFKBH1fgIOb+hvU0U=

Generate the CSR, if you don't have an openssl.cnf, view sample conf below
openssl req -new -sha512 -key ecdsa.key -out cosio.csr -config openssl.cnf

Check the CSR for your domains and ensure crypto
openssl req -in cosio.csr -noout -text

# output
Certificate Request:
    Data:
        Version: 0 (0x0)
        Subject: C=US, ST=California, L=Los Angeles, O=Evan Surdam, CN=esurdam.com/emailAddress=es@cosi.io
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (384 bit)
                pub:
                    23:91:0f:43:2b:b9:5c:60:82:ae:04:38:5f:bc:05:
                    68:d1:93:cf:67:ac:51:5c:ce:82:b3:33:39:5e:74:
                    8b:11:c1:1d:e9:62:c3:8f:e1:fc:54:56:c8:74:01:
                    f2:ec:57:8d:70:90:27:7b:3d:bf:8a:0f:ef:f0:c7:
                    04:20:c4:4a:48:86:8c:84:5b:db:60:3d:2b:fb:79:
                    c1:90:d5:48:23:2a:10:a0:4c:91:e0:c5:bf:a5:42:
                    f5:61:62:0a:23:c0:29
                ASN1 OID: secp384r1
                NIST CURVE: P-384
        Attributes:
        Requested Extensions:
            X509v3 Basic Constraints:
                CA:FALSE
            X509v3 Key Usage:
                Digital Signature, Non Repudiation, Key Encipherment
            X509v3 Subject Alternative Name:
                DNS:esurdam.com, DNS:www.esurdam.com, DNS:evansurdam.com, DNS:www.evansurdam.com
    Signature Algorithm: ecdsa-with-SHA512
         a5:f8:39:b4:c8:2f:a1:ec:3a:e2:9f:e6:25:00:ed:a9:02:31:
         00:aa:31:7b:c1:24:4d:c1:a8:3e:fa:4b:b4:69:a3:09:43:f0:
         30:65:02:30:5f:08:9d:fc:3e:77:40:59:1f:84:3b:e7:57:96:
         fe:c9:75:8f:d9:4c:9b:43:a5:d7:05:0b:eb:fe:c8:b1:a1:99:
         d8:36:de:c7:24:42:00:ef:4a:80:56:5e:30:61:3f:49:b0:da:
         82:de:08:5d:b2:93:00:56:33:1e:6d:af:c0

Use acme-tiny to get it signed. (or certbot, etc.)
python acme_tiny.py --account-key account.key --csr cosio.csr --acme-dir challenges/ > signed.crt

Output should look like:
Parsing account key...
Parsing CSR...
Registering account...
Already registered!
Verifying evansurdam.com...
evansurdam.com verified!
Verifying www.esurdam.com...
www.esurdam.com verified!
Verifying www.evansurdam.com...
www.evansurdam.com verified!
Verifying esurdam.com...
esurdam.com verified!
Signing certificate...
Certificate signed!

If everything goes well you will now have a certificate file that can be used with your private key to host on your site! NginX does require the intermediate file to be appended to the leaf certificate so let's sort that out.
wget -O - https://letsencrypt.org/certs/lets-encrypt-x3-cross-signed.pem > intermediate.pem
cat signed.crt intermediate.pem > chained.pem

Then in nginx
ssl_certificate /path/to/chained.pem;
ssl_certificate_key /path/to/ecsd_key

See Also: Stong SSL + nginx

  
## openssl.cnf
#
# OpenSSL example configuration file.
# This is mostly being used for generation of certificate requests.
#

# This definition stops the following lines choking if HOME isn't
# defined.
HOME			= .
RANDFILE		= $ENV::HOME/.rnd

# Extra OBJECT IDENTIFIER info:
#oid_file		= $ENV::HOME/.oid
oid_section		= new_oids

# To use this configuration file with the "-extfile" option of the
# "openssl x509" utility, name here the section containing the
# X.509v3 extensions to use:
# extensions		=
# (Alternatively, use a configuration file that has only
# X.509v3 extensions in its main [= default] section.)

[ new_oids ]

# We can add new OIDs in here for use by 'ca', 'req' and 'ts'.
# Add a simple OID like this:
# testoid1=1.2.3.4
# Or use config file substitution like this:
# testoid2=${testoid1}.5.6

# Policies used by the TSA examples.
tsa_policy1 = 1.2.3.4.1
tsa_policy2 = 1.2.3.4.5.6
tsa_policy3 = 1.2.3.4.5.7

####################################################################
[ ca ]
default_ca	= CA_default		# The default ca section

####################################################################
[ CA_default ]

dir		= ./demoCA		# Where everything is kept
certs		= $dir/certs		# Where the issued certs are kept
crl_dir		= $dir/crl		# Where the issued crl are kept
database	= $dir/index.txt	# database index file.
#unique_subject	= no			# Set to 'no' to allow creation of
					# several ctificates with same subject.
new_certs_dir	= $dir/newcerts		# default place for new certs.

certificate	= $dir/cacert.pem 	# The CA certificate
serial		= $dir/serial 		# The current serial number
crlnumber	= $dir/crlnumber	# the current crl number
					# must be commented out to leave a V1 CRL
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem# The private key
RANDFILE	= $dir/private/.rand	# private random number file

x509_extensions	= usr_cert		# The extentions to add to the cert

# Comment out the following two lines for the "traditional"
# (and highly broken) format.
name_opt 	= ca_default		# Subject Name options
cert_opt 	= ca_default		# Certificate field options

# Extension copying option: use with caution.
# copy_extensions = copy

# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs
# so this is commented out by default to leave a V1 CRL.
# crlnumber must also be commented out to leave a V1 CRL.
# crl_extensions	= crl_ext

default_days	= 365			# how long to certify for
default_crl_days= 30			# how long before next CRL
default_md	= default		# use public key default MD
preserve	= no			# keep passed DN ordering

# A few difference way of specifying how similar the request should look
# For type CA, the listed attributes must be the same, and the optional
# and supplied fields are just that :-)
policy		= policy_match

# For the CA policy
[ policy_match ]
countryName		= match
stateOrProvinceName	= match
organizationName	= match
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional

# For the 'anything' policy
# At this point in time, you must list all acceptable 'object'
# types.
[ policy_anything ]
countryName		= optional
stateOrProvinceName	= optional
localityName		= optional
organizationName	= optional
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional

####################################################################
[ req ]
default_bits		= 4096
default_keyfile 	= privkey.pem
distinguished_name	= req_distinguished_name
attributes		= req_attributes
x509_extensions	= v3_ca	# The extentions to add to the self signed cert

# Passwords for private keys if not present they will be prompted for
# input_password = secret
# output_password = secret

# This sets a mask for permitted string types. There are several options.
# default: PrintableString, T61String, BMPString.
# pkix	 : PrintableString, BMPString (PKIX recommendation before 2004)
# utf8only: only UTF8Strings (PKIX recommendation after 2004).
# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).
# MASK:XXXX a literal mask value.
# WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings.
string_mask = utf8only

req_extensions = v3_req # The extensions to add to a certificate request

[ req_distinguished_name ]
countryName			= Country Name (2 letter code)
countryName_default		= AU
countryName_min			= 2
countryName_max			= 2

stateOrProvinceName		= State or Province Name (full name)
stateOrProvinceName_default	= Some-State

localityName			= Locality Name (eg, city)

0.organizationName		= Organization Name (eg, company)
0.organizationName_default	= Internet Widgits Pty Ltd

# we can do this but it is not needed normally :-)
#1.organizationName		= Second Organization Name (eg, company)
#1.organizationName_default	= World Wide Web Pty Ltd

organizationalUnitName		= Organizational Unit Name (eg, section)
#organizationalUnitName_default	=

commonName			= Common Name (e.g. server FQDN or YOUR name)
commonName_max			= 64

emailAddress			= Email Address
emailAddress_max		= 64

# SET-ex3			= SET extension number 3

[ req_attributes ]
challengePassword		= A challenge password
challengePassword_min		= 4
challengePassword_max		= 20

unstructuredName		= An optional company name

[ usr_cert ]

# These extensions are added when 'ca' signs a request.

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

basicConstraints=CA:FALSE

# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.

# This is OK for an SSL server.
# nsCertType			= server

# For an object signing certificate this would be used.
# nsCertType = objsign

# For normal client use this is typical
# nsCertType = client, email

# and for everything including object signing:
# nsCertType = client, email, objsign

# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

# This will be displayed in Netscape's comment listbox.
nsComment			= "OpenSSL Generated Certificate"

# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer

# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren't
# deprecated according to PKIX.
# subjectAltName=email:move

# Copy subject details
# issuerAltName=issuer:copy

#nsCaRevocationUrl		= http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName

# This is required for TSA certificates.
# extendedKeyUsage = critical,timeStamping

[ v3_req ]

# Extensions to add to a certificate request

basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment
subjectAltName = @alt_names

[ alt_names ]

DNS.1 = esurdam.com
DNS.2 = www.esurdam.com
DNS.3 = evansurdam.com
DNS.4 = www.evansurdam.com

[ v3_ca ]
# Extensions for a typical CA
# PKIX recommendation.

subjectKeyIdentifier=hash

authorityKeyIdentifier=keyid:always,issuer

# This is what PKIX recommends but some broken software chokes on critical
# extensions.
#basicConstraints = critical,CA:true
# So we do this instead.
basicConstraints = CA:true

# Key usage: this is typical for a CA certificate. However since it will
# prevent it being used as an test self-signed certificate it is best
# left out by default.
# keyUsage = cRLSign, keyCertSign

# Some might want this also
# nsCertType = sslCA, emailCA

# Include email address in subject alt name: another PKIX recommendation
# subjectAltName=email:copy
# Copy issuer details
# issuerAltName=issuer:copy

# DER hex encoding of an extension: beware experts only!
# obj=DER:02:03
# Where 'obj' is a standard or added object
# You can even override a supported extension:
# basicConstraints= critical, DER:30:03:01:01:FF

[ crl_ext ]

# CRL extensions.
# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.

# issuerAltName=issuer:copy
authorityKeyIdentifier=keyid:always

[ proxy_cert_ext ]
# These extensions should be added when creating a proxy certificate

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

basicConstraints=CA:FALSE

# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.

# This is OK for an SSL server.
# nsCertType			= server

# For an object signing certificate this would be used.
# nsCertType = objsign

# For normal client use this is typical
# nsCertType = client, email

# and for everything including object signing:
# nsCertType = client, email, objsign

# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

# This will be displayed in Netscape's comment listbox.
nsComment			= "OpenSSL Generated Certificate"

# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer

# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren't
# deprecated according to PKIX.
# subjectAltName=email:move

# Copy subject details
# issuerAltName=issuer:copy

#nsCaRevocationUrl		= http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName

# This really needs to be in place for it to be a proxy certificate.
proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo

####################################################################
[ tsa ]

default_tsa = tsa_config1	# the default TSA section

[ tsa_config1 ]

# These are used by the TSA reply generation only.
dir		= ./demoCA		# TSA root directory
serial		= $dir/tsaserial	# The current serial number (mandatory)
crypto_device	= builtin		# OpenSSL engine to use for signing
signer_cert	= $dir/tsacert.pem 	# The TSA signing certificate
					# (optional)
certs		= $dir/cacert.pem	# Certificate chain to include in reply
					# (optional)
signer_key	= $dir/private/tsakey.pem # The TSA private key (optional)

default_policy	= tsa_policy1		# Policy if request did not specify it
					# (optional)
other_policies	= tsa_policy2, tsa_policy3	# acceptable policies (optional)
digests		= md5, sha1		# Acceptable message digests (mandatory)
accuracy	= secs:1, millisecs:500, microsecs:100	# (optional)
clock_precision_digits  = 0	# number of digits after dot. (optional)
ordering		= yes	# Is ordering defined for timestamps?
				# (optional, default: no)
tsa_name		= yes	# Must the TSA name be included in the reply?
				# (optional, default: no)
ess_cert_id_chain	= no	# Must the ESS cert id chain be included?
				# (optional, default: no)
	#
	# OpenSSL example configuration file.
	# This is mostly being used for generation of certificate requests.
	#

	# This definition stops the following lines choking if HOME isn't
	# defined.
	HOME = .
	RANDFILE = $ENV::HOME/.rnd

	# Extra OBJECT IDENTIFIER info:
	#oid_file = $ENV::HOME/.oid
	oid_section = new_oids

	# To use this configuration file with the "-extfile" option of the
	# "openssl x509" utility, name here the section containing the
	# X.509v3 extensions to use:
	# extensions =
	# (Alternatively, use a configuration file that has only
	# X.509v3 extensions in its main [= default] section.)

	[ new_oids ]

	# We can add new OIDs in here for use by 'ca', 'req' and 'ts'.
	# Add a simple OID like this:
	# testoid1=1.2.3.4
	# Or use config file substitution like this:
	# testoid2=${testoid1}.5.6

	# Policies used by the TSA examples.
	tsa_policy1 = 1.2.3.4.1
	tsa_policy2 = 1.2.3.4.5.6
	tsa_policy3 = 1.2.3.4.5.7

	####################################################################
	[ ca ]
	default_ca = CA_default # The default ca section

	####################################################################
	[ CA_default ]

	dir = ./demoCA # Where everything is kept
	certs = $dir/certs # Where the issued certs are kept
	crl_dir = $dir/crl # Where the issued crl are kept
	database = $dir/index.txt # database index file.
	#unique_subject = no # Set to 'no' to allow creation of
	# several ctificates with same subject.
	new_certs_dir = $dir/newcerts # default place for new certs.

	certificate = $dir/cacert.pem # The CA certificate
	serial = $dir/serial # The current serial number
	crlnumber = $dir/crlnumber # the current crl number
	# must be commented out to leave a V1 CRL
	crl = $dir/crl.pem # The current CRL
	private_key = $dir/private/cakey.pem# The private key
	RANDFILE = $dir/private/.rand # private random number file

	x509_extensions = usr_cert # The extentions to add to the cert

	# Comment out the following two lines for the "traditional"
	# (and highly broken) format.
	name_opt = ca_default # Subject Name options
	cert_opt = ca_default # Certificate field options

	# Extension copying option: use with caution.
	# copy_extensions = copy

	# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs
	# so this is commented out by default to leave a V1 CRL.
	# crlnumber must also be commented out to leave a V1 CRL.
	# crl_extensions = crl_ext

	default_days = 365 # how long to certify for
	default_crl_days= 30 # how long before next CRL
	default_md = default # use public key default MD
	preserve = no # keep passed DN ordering

	# A few difference way of specifying how similar the request should look
	# For type CA, the listed attributes must be the same, and the optional
	# and supplied fields are just that :-)
	policy = policy_match

	# For the CA policy
	[ policy_match ]
	countryName = match
	stateOrProvinceName = match
	organizationName = match
	organizationalUnitName = optional
	commonName = supplied
	emailAddress = optional

	# For the 'anything' policy
	# At this point in time, you must list all acceptable 'object'
	# types.
	[ policy_anything ]
	countryName = optional
	stateOrProvinceName = optional
	localityName = optional
	organizationName = optional
	organizationalUnitName = optional
	commonName = supplied
	emailAddress = optional

	####################################################################
	[ req ]
	default_bits = 4096
	default_keyfile = privkey.pem
	distinguished_name = req_distinguished_name
	attributes = req_attributes
	x509_extensions = v3_ca # The extentions to add to the self signed cert

	# Passwords for private keys if not present they will be prompted for
	# input_password = secret
	# output_password = secret

	# This sets a mask for permitted string types. There are several options.
	# default: PrintableString, T61String, BMPString.
	# pkix : PrintableString, BMPString (PKIX recommendation before 2004)
	# utf8only: only UTF8Strings (PKIX recommendation after 2004).
	# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).
	# MASK:XXXX a literal mask value.
	# WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings.
	string_mask = utf8only

	req_extensions = v3_req # The extensions to add to a certificate request

	[ req_distinguished_name ]
	countryName = Country Name (2 letter code)
	countryName_default = AU
	countryName_min = 2
	countryName_max = 2

	stateOrProvinceName = State or Province Name (full name)
	stateOrProvinceName_default = Some-State

	localityName = Locality Name (eg, city)

	0.organizationName = Organization Name (eg, company)
	0.organizationName_default = Internet Widgits Pty Ltd

	# we can do this but it is not needed normally :-)
	#1.organizationName = Second Organization Name (eg, company)
	#1.organizationName_default = World Wide Web Pty Ltd

	organizationalUnitName = Organizational Unit Name (eg, section)
	#organizationalUnitName_default =

	commonName = Common Name (e.g. server FQDN or YOUR name)
	commonName_max = 64

	emailAddress = Email Address
	emailAddress_max = 64

	# SET-ex3 = SET extension number 3

	[ req_attributes ]
	challengePassword = A challenge password
	challengePassword_min = 4
	challengePassword_max = 20

	unstructuredName = An optional company name

	[ usr_cert ]

	# These extensions are added when 'ca' signs a request.

	# This goes against PKIX guidelines but some CAs do it and some software
	# requires this to avoid interpreting an end user certificate as a CA.

	basicConstraints=CA:FALSE

	# Here are some examples of the usage of nsCertType. If it is omitted
	# the certificate can be used for anything except object signing.

	# This is OK for an SSL server.
	# nsCertType = server

	# For an object signing certificate this would be used.
	# nsCertType = objsign

	# For normal client use this is typical
	# nsCertType = client, email

	# and for everything including object signing:
	# nsCertType = client, email, objsign

	# This is typical in keyUsage for a client certificate.
	# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

	# This will be displayed in Netscape's comment listbox.
	nsComment = "OpenSSL Generated Certificate"

	# PKIX recommendations harmless if included in all certificates.
	subjectKeyIdentifier=hash
	authorityKeyIdentifier=keyid,issuer

	# This stuff is for subjectAltName and issuerAltname.
	# Import the email address.
	# subjectAltName=email:copy
	# An alternative to produce certificates that aren't
	# deprecated according to PKIX.
	# subjectAltName=email:move

	# Copy subject details
	# issuerAltName=issuer:copy

	#nsCaRevocationUrl = http://www.domain.dom/ca-crl.pem
	#nsBaseUrl
	#nsRevocationUrl
	#nsRenewalUrl
	#nsCaPolicyUrl
	#nsSslServerName

	# This is required for TSA certificates.
	# extendedKeyUsage = critical,timeStamping

	[ v3_req ]

	# Extensions to add to a certificate request

	basicConstraints = CA:FALSE
	keyUsage = nonRepudiation, digitalSignature, keyEncipherment
	subjectAltName = @alt_names

	[ alt_names ]

	DNS.1 = esurdam.com
	DNS.2 = www.esurdam.com
	DNS.3 = evansurdam.com
	DNS.4 = www.evansurdam.com

	[ v3_ca ]
	# Extensions for a typical CA
	# PKIX recommendation.

	subjectKeyIdentifier=hash

	authorityKeyIdentifier=keyid:always,issuer

	# This is what PKIX recommends but some broken software chokes on critical
	# extensions.
	#basicConstraints = critical,CA:true
	# So we do this instead.
	basicConstraints = CA:true

	# Key usage: this is typical for a CA certificate. However since it will
	# prevent it being used as an test self-signed certificate it is best
	# left out by default.
	# keyUsage = cRLSign, keyCertSign

	# Some might want this also
	# nsCertType = sslCA, emailCA

	# Include email address in subject alt name: another PKIX recommendation
	# subjectAltName=email:copy
	# Copy issuer details
	# issuerAltName=issuer:copy

	# DER hex encoding of an extension: beware experts only!
	# obj=DER:02:03
	# Where 'obj' is a standard or added object
	# You can even override a supported extension:
	# basicConstraints= critical, DER:30:03:01:01:FF

	[ crl_ext ]

	# CRL extensions.
	# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.

	# issuerAltName=issuer:copy
	authorityKeyIdentifier=keyid:always

	[ proxy_cert_ext ]
	# These extensions should be added when creating a proxy certificate

	# This goes against PKIX guidelines but some CAs do it and some software
	# requires this to avoid interpreting an end user certificate as a CA.

	basicConstraints=CA:FALSE

	# Here are some examples of the usage of nsCertType. If it is omitted
	# the certificate can be used for anything except object signing.

	# This is OK for an SSL server.
	# nsCertType = server

	# For an object signing certificate this would be used.
	# nsCertType = objsign

	# For normal client use this is typical
	# nsCertType = client, email

	# and for everything including object signing:
	# nsCertType = client, email, objsign

	# This is typical in keyUsage for a client certificate.
	# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

	# This will be displayed in Netscape's comment listbox.
	nsComment = "OpenSSL Generated Certificate"

	# PKIX recommendations harmless if included in all certificates.
	subjectKeyIdentifier=hash
	authorityKeyIdentifier=keyid,issuer

	# This stuff is for subjectAltName and issuerAltname.
	# Import the email address.
	# subjectAltName=email:copy
	# An alternative to produce certificates that aren't
	# deprecated according to PKIX.
	# subjectAltName=email:move

	# Copy subject details
	# issuerAltName=issuer:copy

	#nsCaRevocationUrl = http://www.domain.dom/ca-crl.pem
	#nsBaseUrl
	#nsRevocationUrl
	#nsRenewalUrl
	#nsCaPolicyUrl
	#nsSslServerName

	# This really needs to be in place for it to be a proxy certificate.
	proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo

	####################################################################
	[ tsa ]

	default_tsa = tsa_config1 # the default TSA section

	[ tsa_config1 ]

	# These are used by the TSA reply generation only.
	dir = ./demoCA # TSA root directory
	serial = $dir/tsaserial # The current serial number (mandatory)
	crypto_device = builtin # OpenSSL engine to use for signing
	signer_cert = $dir/tsacert.pem # The TSA signing certificate
	# (optional)
	certs = $dir/cacert.pem # Certificate chain to include in reply
	# (optional)
	signer_key = $dir/private/tsakey.pem # The TSA private key (optional)

	default_policy = tsa_policy1 # Policy if request did not specify it
	# (optional)
	other_policies = tsa_policy2, tsa_policy3 # acceptable policies (optional)
	digests = md5, sha1 # Acceptable message digests (mandatory)
	accuracy = secs:1, millisecs:500, microsecs:100 # (optional)
	clock_precision_digits = 0 # number of digits after dot. (optional)
	ordering = yes # Is ordering defined for timestamps?
	# (optional, default: no)
	tsa_name = yes # Must the TSA name be included in the reply?
	# (optional, default: no)
	ess_cert_id_chain = no # Must the ESS cert id chain be included?
	# (optional, default: no)