Skip to content

Instantly share code, notes, and snippets.

@tsaarni
Created October 22, 2016 08:50
  • Star 39 You must be signed in to star a gist
  • Fork 11 You must be signed in to fork a gist
Star You must be signed in to star a gist
Embed
What would you like to do?
Generate self-signed certs with different key types
*** RSA
# Generate self-signed certificate with RSA 4096 key-pair
openssl req -x509 -nodes -days 3650 -newkey rsa:4096 -keyout rsakey.pem -out rsacert.pem
# print private and public key
openssl rsa -in rsakey.pem -text -noout
# print certificate
openssl x509 -in rsacert.pem -text -noout
# generate PKCS#12 container
openssl pkcs12 -export -inkey rsakey.pem -in rsacert.pem -out rsacred.p12
*** ECDSA
# Generate self-signed certificate with ECDSA using two common curves
openssl req -x509 -nodes -days 3650 -newkey ec:<(openssl ecparam -name prime256v1) -keyout ecdsakey.pem -out ecdsacert.pem
openssl req -x509 -nodes -days 3650 -newkey ec:<(openssl ecparam -name secp384r1) -keyout ecdsakey.pem -out ecdsacert.pem
# print private and public key + curve name
openssl ec -in ecdsakey.pem -text -noout
# print certificate
openssl x509 -in ecdsacert.pem -text -noout
# generate container
openssl pkcs12 -export -inkey ecdsakey.pem -in ecdsacert.pem -out ecdsacred.p12
Which curve to choose?
http://security.stackexchange.com/questions/78621/which-elliptic-curve-should-i-use
"Interoperability" means that you would probably prefer it if SSL clients can actually
connect to your server; otherwise, having a SSL server would be rather pointless.
This simplifies the question a lot: in practice, average clients only support two curves,
the ones which are designated in so-called NSA Suite B: these are NIST curves P-256 and
P-384 (in OpenSSL, they are designated as, respectively, "prime256v1" and "secp384r1").
If you use any other curve, then some widespread Web browsers (e.g. Internet Explorer,
Firefox...) will be unable to talk to your server.
*** DSA
# generate both key and DSA parameters (both will be stored in dsakey.pem)
openssl dsaparam -genkey 1024 -out dsakey.pem
openssl req -x509 -new -days 3650 -key dsakey.pem -out dsacert.pem
# print private and public key with DSA params
openssl dsa -in dsakey.pem -text -noout
# print certificate
openssl x509 -in dsacert.pem -text -noout
# print only DSA params from key file
openssl dsaparam -in dsakey.pem -text -noout
# generate container
openssl pkcs12 -export -inkey dsakey.pem -in dsacert.pem -out dsacred.p12
*** Test TLS connection
openssl s_server -accept 1443 -www -key key.pem -cert cert.pem
openssl s_client -showcerts -connect localhost:1443 -CAfile cert.pem
@imron543
Copy link

This is very useful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment