Ovahlord · March 7, 2024 15:03
diff --git a/Convert openssl .key file to .pem b/Convert openssl .key file to .pem
 For converting .key file to .pem file,

 Your keys may already be in PEM format, but just named with .crt or .key.

 If they begin with -----BEGIN and you can read them in a text editor (they use base64, which is readable in ASCII, not binary format), they are in PEM format.

 If the file is in binary, for the server.crt, you would use 
 	openssl x509 -inform DER -outform PEM -in server.crt -out server.crt.pem

 	For server.key, use openssl rsa in place of openssl x509.

 The server.key is likely your private key, and the .crt file is the returned, signed, x509 certificate.

 If this is for a Web server, and you cannot specify loading a separate private and public key, you may need to concatenate the two files. For this use: cat server.crt server.key > server.includesprivatekey.pem. I would recommend naming files with "includesprivatekey" to help you manage the permissions you keep with this file.
	For converting .key file to .pem file,

	Your keys may already be in PEM format, but just named with .crt or .key.

	If they begin with -----BEGIN and you can read them in a text editor (they use base64, which is readable in ASCII, not binary format), they are in PEM format.

	If the file is in binary, for the server.crt, you would use
	openssl x509 -inform DER -outform PEM -in server.crt -out server.crt.pem

	For server.key, use openssl rsa in place of openssl x509.

	The server.key is likely your private key, and the .crt file is the returned, signed, x509 certificate.

	If this is for a Web server, and you cannot specify loading a separate private and public key, you may need to concatenate the two files. For this use: cat server.crt server.key > server.includesprivatekey.pem. I would recommend naming files with "includesprivatekey" to help you manage the permissions you keep with this file.