Skip to main content

I made a GIF!

Subject alternative names and signing certificates with OpenSSL

There are very good how-tos on creating an openssl configuration file with the necessary subject alternative name extensions.  Copy the entire "openssl.cfg" and save it as as "subaltname.cfg" and add the following lines in the "rec" and "v3_req" sections:
[ req ]
req_extensions   = v3_req
[ v3_req ]
subjectAltName   = DNS:srv.example.com; IP:172.16.0.10 

extendedKeyUsage = serverAuth, clientAuth
NOTE: Extended Key Usage is not required, but is included as many applications using Subject Alternative Names use the generated SSL certificates for both purposes.

Generating the certificate signing request (CSR) requires using the command line option "-config [filename]".  
# openssl req -new -newkey rsa:2048 -sha256 \ 
-nodes -out rui.csr -keyout rui.key \  
-config subaltname.cfg
Verify the CSR contains the X509v3 Subject Alternative Name.
# openssl req -in rui.csr -noout -text
[...]
X509v3 Subject Alternative Name:
 DNS:srv.example.com,  IP Address:172.16.0.10
[...]
Likewise certificate generation requires using the command line option(s) too.  However they are not the same options; use "-extfile [filename] -extensions v3_req" instead.
# openssl x509 -req -CA ca.crt -CAkey ca.key \ 
-set_serial 01 -days 2880 -in srv.csr -out srv.crt \
-extfile subaltname.cfg -extensions v3_req
 Again verify the certificate contains the X509v3 Subject Alternative Name.
# openssl x509 -in rui.crt -text -noout
[...]
X509v3 Subject Alternative Name:
 DNS:srv.example.com,  IP Address:172.16.0.10
[...]

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

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

Comments

Anonymous said…
Old post but helped me a lot.
Cheers!

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