red_led red-led

Two ways to do it, but only worked for me so I'll put it first and the second for reference:

$ openssl pkcs12 -export -in hostname.crt -inkey hostname.key -out hostname.p12
$ openssl pkcs12 -in hostname.p12 -nodes -out hostname.pem

Other options for this method in comments below:

# Note, the -certfile root.crt appends all CA certs to the export, I've never needed these so it's optional for my personal steps
$ openssl pkcs12 -export -in hostname.crt -inkey hostname.key -certfile root.crt -out hostname.p12

Note, I've always had my hostname.crt as part of my .pem, so I keep my certs but apparently you may not have to, hence the nocerts flag being an extra option in this sample

	# One liner for counting unique IP addresses from nginx logs
	# Feel free to comment with better ideas - I'm sure it's not the best way of doing this (I'm no awk ninja!)
	#
	# Sample output:
	#
	# $ cat example.com.access.log \| awk -F " " '{a[$1]++ } END { for (b in a) { print b, "\t", a[b] } }'
	# 66.65.145.220 49
	# 92.63.28.68 126

	cat example.com.access.log \| awk -F " " '{a[$1]++ } END { for (b in a) { print b, "\t", a[b] } }'

	source: http://www.markbrilman.nl/2011/08/howto-convert-a-pfx-to-a-seperate-key-crt-file/

	`openssl pkcs12 -in [yourfile.pfx] -nocerts -out [keyfile-encrypted.key]`

	What this command does is extract the private key from the .pfx file. Once entered you need to type in the importpassword of the .pfx file. This is the password that you used to protect your keypair when you created your .pfx file. If you cannot remember it anymore you can just throw your .pfx file away, cause you won’t be able to import it again, anywhere!. Once you entered the import password OpenSSL requests you to type in another password, twice!. This new password will protect your .key file.

	Now let’s extract the certificate:

	`openssl pkcs12 -in [yourfile.pfx] -clcerts -nokeys -out [certificate.crt]`