• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Why is Plesk still generating sha1 certs?!

H

HostaHost

Regular Pleskian
Most modern browsers are now flagging sha1 certs as insecure, whether it be something simple like a URL bar color change on the padlock to a caution flag, or with Chrome, clicking into the details tells you the site is using "obsolete encryption". Odin has known about the issue for at least eight months (http://kb.odin.com/en/123904) and released that kb on how to work around it. Yet here we are, Plesk 12 still doesn't make that change itself so that new servers generate SHA2 csr's....
 
Hello,

As Google begun flagging sites with recent SHA1 cert, this is a big problem. I think we don´t have to wait a general update of plesk to fix this critical issue. Any shopping site under plesk 12 is flag as insecure by chrome. This is a HUGE problem. May you have to cosider to fix it as a Microupdate as soon as possible.

In the meantime I don´t know if somebody know how to generate a CSR with SHA256 encryption. Thanks
 
IgorG said:
Yes, we aware on this issue and have corresponding feature request http://plesk.uservoice.com/forums/1...-sha256-sha-2-for-certificate-reques#comments
I think it will be fixed in one of updates of upcoming Plesk 12.5 version.
Click to expand...

It is a ONE LINE change in ONE FILE; does that really require a major version update instead of just a micro update to add "default_md = sha256" to /usr/local/psa/admin/conf/openssl.cnf?

Why does it seem like a constant battle to get Odin to update Plesk with current security standards?
 
Hello,

I followed this KB article http://kb.odin.com/en/123904

And try to generate a new CSR for a new SSL certificate but the length of the CSR is the same so I think is not signed with SHA2. Do I have to restart something or do something more?
 
Not that I've seen. On servers where we've changed it, any CSR's generated after that point have been sha2. You can confirm this by pasting the CSR into a file and running "openssl req -noout -text -in FILENAME" and you should see it mention sha256.
 
You must log in or register to reply here.
Back
Top