Unable to create Version 3 certificates with subjectAltName using my own CA

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Unable to create Version 3 certificates with subjectAltName using my own CA

Hum Brai
Summary: CSR has x509v3 extensions, certificate does not


Working with CentOS 6.2, openssl version:
OpenSSL 1.0.0-fips 29 Mar 2010

I created my own CA certificate using:

openssl req -new -x509 -days 365 -key host.example.com_CA.key -out
host.example.com_CA.crt

I found on internet how we can make CSR (request) have subjectAltName,
this works good. See cnf file changes below.

Request made with this:

openssl req -new -key user-host.example.com.key -out user-host.example.com.csr

Verified it has requested x509v3 extensions including the email
address in subjectAltName

PROBLEM is when take a request to make new user certificate, I get no
x509v3 fields in certificate like subjectAltName and the certificate
is in Version 1, not Version 3. I thought putting copy_extensions=copy
in the CA_default fix this, but not true.

Created user cert with this:

openssl x509 -req -days 365 -in user-host.example.com.csr -CA
host.example.com_CA.crt -CAkey host.example.com_CA.key -CAcreateserial
-CAserial serial_numbers -out user-host.example.com.crt

Can someone help me? Below full config file, only 3 changes I made to it:

1. uncomment copy_extensions=copy in [CA_default]
2. uncomment req_extensions=v3_req in [req]
3. add subjectAltName=email:copy to [v3_req]

I tried other things too I saw on internet but nothing helping.  here is config:


#
# 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             = /etc/pki/CA           # 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            = 2048
default_md              = sha1
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             = XX
countryName_min                 = 2
countryName_max                 = 2

stateOrProvinceName             = State or Province Name (full name)
#stateOrProvinceName_default    = Default Province

localityName                    = Locality Name (eg, city)
localityName_default    = Default City

0.organizationName              = Organization Name (eg, company)
0.organizationName_default      = Default Company 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 (eg, your name or your
server\'s hostname)
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=email:copy

[ 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 Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

RE: *** Spam *** Unable to create Version 3 certificates with subjectAltName using my own CA

Dave Thompson-5
> From: [hidden email] On Behalf Of Hum Brai
> Sent: Friday, October 04, 2013 12:00

> Summary: CSR has x509v3 extensions, certificate does not
<snip>
> I found on internet how we can make CSR (request) have subjectAltName,
(and verified)

> PROBLEM is when take a request to make new user certificate, I get no
> x509v3 fields in certificate like subjectAltName and the certificate
> is in Version 1, not Version 3. I thought putting copy_extensions=copy
> in the CA_default fix this, but not true.
>
> Created user cert with this:
>
> openssl x509 -req -days 365 -in user-host.example.com.csr -CA
> host.example.com_CA.crt -CAkey host.example.com_CA.key -CAcreateserial
> -CAserial serial_numbers -out user-host.example.com.crt

OpenSSL has two ways to create a cert from a CSR:
'ca' # the original most complete way
'x509 -req' # a simplified way without the 'database' etc.

Only 'ca' fully uses the config file settings and in particular
copy_extensions.
'x509 -req' can use the config file for extensions but nothing else.

Use 'ca' if you want to copy extensions from the CSR.

You *can* use 'x509 -req' and put extensions including SAN in the config
file
at 'x509 -req' time (not 'req -new' time), and that's good for CA-related
extensions like crldp, but you usually want SAN to vary for each cert.

<snip rest>


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: *** Spam *** Unable to create Version 3 certificates with subjectAltName using my own CA

Hum Brai
Oh, sorry my message got labeled as spam, is it because I pasted the
conf?  THANK YOU for replying anyway.  Question:

>> Summary: CSR has x509v3 extensions, certificate does not
> <snip>
>> I found on internet how we can make CSR (request) have subjectAltName,
> (and verified)
>
>> PROBLEM is when take a request to make new user certificate, I get no
>> x509v3 fields in certificate like subjectAltName and the certificate
>> is in Version 1, not Version 3. I thought putting copy_extensions=copy
>> in the CA_default fix this, but not true.
>>
>> Created user cert with this:
>>
>> openssl x509 -req -days 365 -in user-host.example.com.csr -CA
>> host.example.com_CA.crt -CAkey host.example.com_CA.key -CAcreateserial
>> -CAserial serial_numbers -out user-host.example.com.crt
>
> OpenSSL has two ways to create a cert from a CSR:
> 'ca' # the original most complete way
> 'x509 -req' # a simplified way without the 'database' etc.
>
> Only 'ca' fully uses the config file settings and in particular
> copy_extensions.

Ohhhhhh! I wish that documented. :)

> 'x509 -req' can use the config file for extensions but nothing else.
>
> Use 'ca' if you want to copy extensions from the CSR.
>
> You *can* use 'x509 -req' and put extensions including SAN in the config
> file
> at 'x509 -req' time (not 'req -new' time), and that's good for CA-related
> extensions like crldp, but you usually want SAN to vary for each cert.

Yes correct, but can't SAN email:copy make unique every cert? I only
want this extetnsion, doesnt need come from request. Can I still use
x509 -req for this? I did try the command adding "-extensions v3_req"
but didn't do anything. Did I do it wrong?

Thanks again!
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: *** Spam *** Unable to create Version 3 certificates with subjectAltName using my own CA

Hum Brai
On 10/4/13, Hum Brai <[hidden email]> wrote:

> Oh, sorry my message got labeled as spam, is it because I pasted the
> conf?  THANK YOU for replying anyway.  Question:
>
>>> Summary: CSR has x509v3 extensions, certificate does not
>> <snip>
>>> I found on internet how we can make CSR (request) have subjectAltName,
>> (and verified)
>>
>>> PROBLEM is when take a request to make new user certificate, I get no
>>> x509v3 fields in certificate like subjectAltName and the certificate
>>> is in Version 1, not Version 3. I thought putting copy_extensions=copy
>>> in the CA_default fix this, but not true.
>>>
>>> Created user cert with this:
>>>
>>> openssl x509 -req -days 365 -in user-host.example.com.csr -CA
>>> host.example.com_CA.crt -CAkey host.example.com_CA.key -CAcreateserial
>>> -CAserial serial_numbers -out user-host.example.com.crt
>>
>> OpenSSL has two ways to create a cert from a CSR:
>> 'ca' # the original most complete way
>> 'x509 -req' # a simplified way without the 'database' etc.
>>
>> Only 'ca' fully uses the config file settings and in particular
>> copy_extensions.
>
> Ohhhhhh! I wish that documented. :)
>
>> 'x509 -req' can use the config file for extensions but nothing else.
>>
>> Use 'ca' if you want to copy extensions from the CSR.
>>
>> You *can* use 'x509 -req' and put extensions including SAN in the config
>> file
>> at 'x509 -req' time (not 'req -new' time), and that's good for CA-related
>> extensions like crldp, but you usually want SAN to vary for each cert.
>
> Yes correct, but can't SAN email:copy make unique every cert? I only
> want this extetnsion, doesnt need come from request. Can I still use
> x509 -req for this? I did try the command adding "-extensions v3_req"
> but didn't do anything. Did I do it wrong?

Yes! I missing "-extfile PATH". Now SAN email:copy works!

Followup quetsion. If I want to generate SAN with DNSName for only one
certificate, this same process work? Just change v3_req in conf file
with the DNSName?
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Unable to create Version 3 certificates with subjectAltName using my own CA

Hum Brai
In reply to this post by Hum Brai
Everything good now. Solution below. Thank to Dave very much.

>>>> Summary: CSR has x509v3 extensions, certificate does not
>>> <snip>
>>>> I found on internet how we can make CSR (request) have subjectAltName,
>>> (and verified)
>>>
>>>> PROBLEM is when take a request to make new user certificate, I get no
>>>> x509v3 fields in certificate like subjectAltName and the certificate
>>>> is in Version 1, not Version 3. I thought putting copy_extensions=copy
>>>> in the CA_default fix this, but not true.
>>>>
>>>> Created user cert with this:
>>>>
>>>> openssl x509 -req -days 365 -in user-host.example.com.csr -CA
>>>> host.example.com_CA.crt -CAkey host.example.com_CA.key -CAcreateserial
>>>> -CAserial serial_numbers -out user-host.example.com.crt
>>>
>>> OpenSSL has two ways to create a cert from a CSR:
>>> 'ca' # the original most complete way
>>> 'x509 -req' # a simplified way without the 'database' etc.
>>>
>>> Only 'ca' fully uses the config file settings and in particular
>>> copy_extensions.
>>
>>> You *can* use 'x509 -req' and put extensions including SAN in the config
>>> file
>>> at 'x509 -req' time (not 'req -new' time), and that's good for
>>> CA-related
>>> extensions like crldp, but you usually want SAN to vary for each cert.

So I can release some of my changes to conf file. Only need ONE change! This:

1. add subjectAltName=email:copy to [v3_req]

Note if you want server certificate, change to
subjectAltName=DNS:host.example.com

Now corrected command with missing -extensions and -extfile

openssl x509 -req -days 365 -in user-host.example.com.csr -CA
host.example.com_CA.crt -CAkey host.example.com_CA.key -CAcreateserial
-CAserial serial_numbers -out user-host.example.com.crt -extensions
v3_req -extfile /etc/pki/tls/openssl.cnf
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]