2 ms·
Author here. This is a long but, but here's the gist: - sha256 is required for Chrome 42+ (mid April 2015) not to show warnings. - 2048 bit RSA is the new Ope
by nailer 12y ago
Author here. This is a long but, but here's the gist:
- sha256 is required for Chrome 42+ (mid April 2015) not to show warnings.
- 2048 bit RSA is the new OpenSSL default and is required for EV certificates.
- The 'subject' (the thing being attested to by the CA) you actually get in your certificate may have a lot more detail than the subject line in your CSR.
- If you're using EV, and have at least www and non-www, the CN will never be used - your CA will put all the server names inside the SAN fields. Anything else won't work with current browsers.
- discreditable 12y agoTrying it out on my Windows machine, it gives me the PowerShell command to create a certificate. Is there some way to specify that I want an OpenSSL command?
- nailer 12y agoCurrently it assumes Windows servers for Windows browsers. I'll add an override for switching to Unix shell shortly and let you know here when fixed.
- nailer 12y agoHi there - just a quick update to say you can now click 'Windows | Unix and Linux' underneath the command to flip between powershell & certreq / bash & openssl
- timdierks 12y agoAre there really CAs that copy the hash used for the CSR to the hash used for the cert? If not, the hash used in the CSR has nothing to do with Chrome warnings (as the browser will never see it).
- hsivonen 12y agoStartSSL at least a while ago picked up the hash algorithm from the CSR.