Skip to main content

I made a GIF!

Generating Elliptic Curve private keys

Public key cryptography uses private keys to decrypt messages and public keys to encrypt them. Generating a private key is the first step to creating a certificate signing request or a self-signed certificate. Most OpenSSL private key examples suggest creating an RSA private key:

$ openssl genrsa -out private.key 2048

This uses RSA algorithms on semiprimes (the product of similarly sized prime numbers).  Elliptic curve (EC) algorithms are an alternative.  The OpenSSL process requires creating a named parameter file before the private key can be generated.

$ openssl ecparam -out ec-param.pem -name prime256v1
$ openssl ecparam -in ec-param.pem -check -noout -text
ASN1 OID: prime256v1 
checking elliptic curve parameters: ok 
$ openssl ecparam -in ec-param.pem -genkey -out ec-private.key 
$ cat ec-private.key 
-----BEGIN EC PARAMETERS----- 
BggqhkjOPQMBBw== 
-----END EC PARAMETERS------- 
---BEGIN EC PRIVATE KEY-----MHcCAQEEIIa2SkCuXClQOwCoS3uIgFnffXj4fWtJe02aLLPNJ077oAoGCCqGSM49AwEHoUQDQgAEzT8n1Wq/4NvY7uYpJ3cr5cjUG1lExgQSL/CoaLxnOYcsALQWU5ZiUVyhuE6cJr0yz6KTWv6lFAmVcY8nZ9kubw== 
-----END EC PRIVATE KEY-----

The named curve "prime256v1" was selected as an example.  To list all the available curves, run:

$ openssl ecparam -list_curves

The EC private key is drop-in compatible for common CSR and X509 certificate generation:

$ openssl req -key ec-private.key -new -out ec-server.csr 
$ openssl req -key ec-private.key -new -x509 -out ec-public.crt 
$ openssl x509 -in ec-public.crt -noout -text

Very neat!

Your feedback is needed! If this post was helpful, incorrect or could be better, please comment below.

Also see these my SSL related posts:
SSL Management Tasks
SSL Management Tasks Revisited
Retrieve SSL certificates

Comments

Popular posts from this blog

Cisco ASA ICMP packet-tracer

Occasionally devices fail to respond to a ping.  This can result from devices being off-line, having a local firewall enabled or the perimeter firewall configuration.  The Cisco ASA ICMP packet-tracer options differ from the TCP or UDP command options.  An example is below: packet-tracer input outside icmp A.B.C.D 8 0 E.F.G.H The ICMP type is "8" (echo request) with code"0" (none).  There are no options on destination IPv4 address E.F.G.H. Complete ICMP documentation at URL http://www.iana.org/assignments/icmp-parameters/ Complete Cisco ASA packet-tracer documentation at URL http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/p.html#wp1878788

Xfce4 lock screen not working

Xfce4 would not start a screensaver on my Linux system.  Researching it, it ran xflock4 from the command line ad received an error: Property "/general/LockCommand" does not exist on channel "xfce4-session". To fix this, additional configuration needed, but no hacks. First, verify xflock4 and xfconf-query are available. $ which xflock4 xfconf-query /bin/xflock4 /bin/xfconf-query Next  install a lock screen package that provides 'xlock', 'slock', 'i3lock' or similar.  $ sudo yum install -y xlockmore-gtk i3lock Last, add an executable (with options) as /general/LockCommand in the xfce4-session settings. $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "xlock -mode matrix" --type  string $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "i3lock -c 000000" --type string Test by running xflock4 from the command line or through the GUI.

X11 Forwarding issue solved

TL;DR Disabling IPv6 necessitates SSHd AddressFamily is "inet" for X11 Forwarding to work. Issue OpenSSH assumes both IPv6 and IPv4 protocols are enabled, and default SSHd AddressFamily value "any" is valid. Quickly skimming the OpenSSH source code, it was not obvious why SSHd does not fail gracefully, selecting only an available IP address family. Therefore, for X11 Forwarding to work correctly, in /etc/ssh/sshd_config we must choose: Defaults - IPv6 enabled and SSHd AddressFamily value " any " Custom - IPv6 disabled and SSHd AddressFamily value " inet " Background PuTTY was not creating a $HOME/.Xauthority file on ssh login and no X11 applications would run, despite setting $DISPLAY.  PuTTY was correctly configured with: X11 Forwarding enabled X display location empty Remote authentication protocol MIT-Magic-Cookie-1 X authority file for local display empty On the initial ssh login there should be a .Xauthority notic