Commit 658ee16b authored by Leigh Stoller's avatar Leigh Stoller

Convert to prompt=no, with per cert config files. This avoids all

interaction with the user. The main point to note is that for the
clients, there is a localnode.cnf and a ronnode.cnf. The difference is
that I encode the type (pcron) in one of the extra fields so that tmcd
can do a check on it. This is in lieu of per client certs, which would
be a big pain in the butt right now. As we add other remote groups, we
will create new config files. I bet this will change over time, as
we learn more.

Chad, it would be nice the tiptunnel cert could be generated from this
setup.
parent c85e32d6
......@@ -9,15 +9,10 @@ SUBDIR = ssl
include $(OBJDIR)/Makeconf
all:
all: emulab.pem server.pem localnode.pem ronnode.pem
include $(TESTBED_SRCDIR)/GNUmakerules
#
# The openssl config file.
#
SSLCONF = $(SRCDIR)/openssl.cnf
#
# You do not want to run these targets unless you are sure you
# know what you are doing! You really do not want to install these
......@@ -26,58 +21,44 @@ SSLCONF = $(SRCDIR)/openssl.cnf
#
pems: emulab.pem server.pem client.pem
emulab.pem: dirsmade $(SSLCONF)
emulab.pem: dirsmade emulab.cnf
#
# Create the Certificate Authority.
# The certificate (no key!) is installed on both boss and remote nodes.
#
openssl req -new -x509 -config $(SSLCONF) \
openssl req -new -x509 -config emulab.cnf \
-keyout cakey.pem -out cacert.pem
cp cacert.pem emulab.pem
server.pem: dirsmade $(SSLCONF)
server.pem: dirsmade server.cnf ca.cnf
#
# Create the server side private key and certificate request.
#
openssl req -new -config $(SSLCONF) \
-keyout servkey.pem -out servreq.pem
openssl req -new -config server.cnf \
-keyout server_key.pem -out server_req.pem
#
# Combine key and cert request.
#
cat servkey.pem servreq.pem > newreq.pem
cat server_key.pem server_req.pem > newreq.pem
#
# Sign the server cert request, creating a server certificate.
#
openssl ca -policy policy_anything -config $(SSLCONF) \
-out servcert.pem \
openssl ca -batch -policy policy_match -config ca.cnf \
-out server_cert.pem \
-cert cacert.pem -keyfile cakey.pem \
-infiles newreq.pem
#
# Combine the key and the certificate into one file which is installed
# on boss and used by tmcd.
#
cat servkey.pem servcert.pem > server.pem
cat server_key.pem server_cert.pem > server.pem
rm -f newreq.pem
client.pem: dirsmade $(SSLCONF)
#
# Create a client side private key and certificate request.
#
openssl req -new -config $(SSLCONF) \
-keyout clientkey.pem -out clientreq.pem
#
# Sign the client cert request, creating a client certificate.
#
openssl ca -policy policy_anything -config $(SSLCONF) \
-out clientcert.pem \
-cert cacert.pem -keyfile cakey.pem \
-infiles clientreq.pem
#
# Combine the key and the certificate into one file which is installed
# on each remote node and used by tmcc. Installed on boss too so
# we can test tmcc there.
#
cat clientkey.pem clientcert.pem > client.pem
localnode.pem: dirsmade localnode.cnf ca.cnf $(SRCDIR)/mkclient.sh
$(SRCDIR)/mkclient.sh localnode
ronnode.pem: dirsmade ronnode.cnf ca.cnf $(SRCDIR)/mkclient.sh
$(SRCDIR)/mkclient.sh ronnode
dirsmade:
-mkdir -p certs
......@@ -90,15 +71,17 @@ dirsmade:
#
# You do not want to run these targets unless you are sure you
# know what you are doing!
#
#
install:
@echo "BE VERY CAREFUL! INSTALLING NEW CERTS CAN CAUSE DISASTER!"
boss-install: $(INSTALL_ETCDIR)/emulab.pem \
$(INSTALL_ETCDIR)/server.pem \
$(INSTALL_ETCDIR)/client.pem
$(INSTALL_ETCDIR)/server.pem
$(INSTALL_DATA) localnode.pem $(INSTALL_ETCDIR)/client.pem
client-install: $(INSTALL_ETCDIR)/client.pem
client-install:
$(INSTALL_DATA) localnode.pem $(INSTALL_ETCDIR)/client.pem
clean:
rm -f *.pem serial index.txt *.old dirsmade
rm -rf certs crl
rm -f *.pem serial index.txt *.old dirsmade *.cnf
rm -rf newcerts certs
http://www.aboveground.cx/~rjmooney/projects/misc/clientcertauth.html
http://www.stunnel.org/faq/certs.html#ToC1
http://www.ultranet.com/~fhirsch/Papers/cook/ssl_cook.html
http://www.rtfm.com/openssl-examples/
http://www.columbia.edu/~ariel/ssleay/x509_index.html
#
# OpenSSL example configuration file.
# This definition stops the following lines choking if HOME isn't
# defined.
HOME = .
RANDFILE = $ENV::HOME/.rnd
####################################################################
[ ca ]
default_ca = CA_default # The default ca section
prompt = no
####################################################################
[ CA_default ]
dir = . # 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.
new_certs_dir = $dir/newcerts # default place for new certs.
certificate = $dir/cacert.pem # The CA certificate
serial = $dir/serial # The current serial number
crl = $dir/crl.pem # The current CRL
private_key = $dir/cakey.pem # The private key
RANDFILE = $dir/.rand # private random number file
x509_extensions = usr_cert # The extentions to add to the cert
# 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.
# crl_extensions = crl_ext
default_days = 1000 # how long to certify for
default_crl_days= 30 # how long before next CRL
default_md = md5 # which md to use.
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 = match
emailAddress = optional
[ 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
# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer:always
[ req ]
prompt = no
default_bits = 1024
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
encrypt_key = no
string_mask = nombstr
[ req_distinguished_name ]
C = US
ST = Utah
L = Salt Lake City
O = Utah Network Testbed
OU = Certificate Authority
CN = @BOSSNODE@
emailAddress = @TBOPSEMAIL@
[ req_attributes ]
[ v3_ca ]
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid:always,issuer:always
basicConstraints = CA:true
[ req ]
prompt = no
default_bits = 1024
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
encrypt_key = no
string_mask = nombstr
[ req_distinguished_name ]
C = US
ST = Utah
L = Salt Lake City
O = Utah Network Testbed
# tmcd uses OU and CN for verification.
OU = pclocal
CN = @BOSSNODE@
emailAddress = @TBOPSEMAIL@
[ req_attributes ]
[ v3_ca ]
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid:always,issuer:always
basicConstraints = CA:true
#!/bin/sh
prefix=$1
#
# Create a client side private key and certificate request.
#
openssl req -new -config ${prefix}.cnf \
-keyout ${prefix}_key.pem -out ${prefix}_req.pem
#
# Sign the client cert request, creating a client certificate.
#
openssl ca -batch -policy policy_match -config ca.cnf \
-out ${prefix}_cert.pem \
-cert cacert.pem -keyfile cakey.pem \
-infiles ${prefix}_req.pem
#
# Combine the key and the certificate into one file which is installed
# on each remote node and used by tmcc. Installed on boss too so
# we can test tmcc there.
#
cat ${prefix}_key.pem ${prefix}_cert.pem > ${prefix}.pem
exit 0
#
# OpenSSL example configuration file.
# This is mostly being used for generation of certificate requests.
#
# $FreeBSD: src/crypto/openssl/apps/openssl.cnf,v 1.1.1.1.2.3 2000/11/26 11:32:48 kris Exp $
# 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' and 'req'.
# Add a simple OID like this:
# testoid1=1.2.3.4
# Or use config file substitution like this:
# testoid2=${testoid1}.5.6
####################################################################
[ ca ]
default_ca = CA_default # The default ca section
####################################################################
[ CA_default ]
dir = . # 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.
new_certs_dir = $dir/newcerts # default place for new certs.
certificate = $dir/cacert.pem # The CA certificate
serial = $dir/serial # The current serial number
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
# 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.
# crl_extensions = crl_ext
default_days = 365 # how long to certify for
default_crl_days= 30 # how long before next CRL
default_md = md5 # which md to use.
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 = 1024
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
encrypt_key = no
# 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.
# utf8only: only UTF8Strings.
# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).
# MASK:XXXX a literal mask value.
# WARNING: current versions of Netscape crash on BMPStrings or UTF8Strings
# so use this option with caution!
string_mask = nombstr
# req_extensions = v3_req # The extensions to add to a certificate request
[ req_distinguished_name ]
countryName = Country Name (2 letter code)
countryName_default = US
countryName_min = 2
countryName_max = 2
stateOrProvinceName = State or Province Name (full name)
stateOrProvinceName_default = Utah
localityName = Locality Name (eg, city)
localityName_default = Salt Lake City
organizationName = Organization Name (eg, company)
organizationName_default = Utah Network Testbed
organizationalUnitName = Organizational Unit Name (eg, section)
#organizationalUnitName_default =
commonName = Common Name (eg, YOUR name)
commonName_default = Emulab.Net
commonName_max = 64
emailAddress = Email Address
emailAddress_default = testbed-ops@fast.cs.utah.edu
emailAddress_max = 40
# 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:always
# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# Copy subject details
# issuerAltName=issuer:copy
#nsCaRevocationUrl = http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName
[ v3_req ]
# Extensions to add to a certificate request
basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment
[ v3_ca ]
# Extensions for a typical CA
# PKIX recommendation.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid:always,issuer:always
# 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,issuer:always
[ req ]
prompt = no
default_bits = 1024
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
encrypt_key = no
string_mask = nombstr
[ req_distinguished_name ]
C = US
ST = Utah
L = Salt Lake City
O = Utah Network Testbed
# tmcd uses OU and CN for verification.
OU = pcron
CN = @BOSSNODE@
emailAddress = @TBOPSEMAIL@
[ req_attributes ]
[ v3_ca ]
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid:always,issuer:always
basicConstraints = CA:true
[ req ]
prompt = no
default_bits = 1024
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
encrypt_key = no
string_mask = nombstr
[ req_distinguished_name ]
C = US
ST = Utah
L = Salt Lake City
O = Utah Network Testbed
OU = Server
# tmcc uses CN for verification.
CN = @BOSSNODE@
emailAddress = @TBOPSEMAIL@
[ req_attributes ]
[ v3_ca ]
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid:always,issuer:always
basicConstraints = CA:true
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment