Closed alanorth closed 10 years ago
Right, the command I use implies you've already generated a private key file, and that you would change out the your-private.key
filename for our actual key. I tweaked the text in 0ef2d30 to make this clearer.
To be clear, your command is more self-contained, but I'm expecting the end users here to be re-issuing, not creating a key for the first time, and I'm trying to keep that section brief. Open to other changes I can make to make this all clearer.
Ah, yes. Great! Cheers.
This is still a problem.
On Amazon Linux 2015.3 I ran into the same problem as the original poster.
However, I got things to work with this:
openssl req -new -nodes -sha256 -out my-domain.csr -keyout my-domain.key
Go figure, haha
On Arch Linux with
OpenSSL 1.0.1i
and CentOS 6.5OpenSSL 1.0.1e-fips
:For reference, I was able to buy a SHA2 cert from Namecheap (Comodo PositiveSSL) using this: