How to replace Discourse LetsEncrypt Certificate from RSA 4096 bits to ECC 256 bits?
I want this permanent on my install, even after upgrade of discourse, is that possible?
sam
6 أغسطس 2018، 12:36ص
2
@mpalmer does this request make sense to you? Is there anything off with our current certificate config in NGINX?
OK per What is RSA, DSA and ECC? ECC is latest and greatest, so I guess we should at least document how to do this. Not sure.
mpalmer
6 أغسطس 2018، 12:57ص
3
I’m ambivalent on documenting it. The benefits of wholesale replacing an RSA certificate with an ECC one are so niche, and the potential downsides so great, that we’d probably end up with more “I did this thing without considering the consequences AND IT’S ALL YOUR FAULT” topics than “I have a legitimate use case for an ECC cert but can’t figure out how to modify the template to make it happen”.
schleifer
6 أغسطس 2018، 5:38م
6
That’s an empty set. I’d bet on it.
sam
6 أغسطس 2018، 9:46م
7
RoldanLT:
At least maybe give us an option
It is an option you just have to figure out how to write the template and mix it in
Is it enough by editing line 59 & 63 on this file?
Editing line 59 & 63 on /templates/web.letsencrypt.ssl.template.yml didn’t work.
Maybe it will work if I force to renew/generate new cert?
Falco
11 مارس 2021، 1:59ص
13
نفّذ @gerhard هذا في عام 2019
master ← elliptic_curve
merged 11:02PM - 09 Sep 19 UTC
[Mozilla](https://wiki.mozilla.org/Security/Server_Side_TLS) recommends ECDSA (P… -256) as certificate type for intermediate compatibility.
> ECDSA certificates are recommended over RSA certificates, as they allow the use of ECDHE with Windows 7 clients using Internet Explorer 11
Most modern browsers will use cipher suites with the ECDSA certificate. Older browsers will select the RSA certificate and a RSA cipher suite.
It will create two Let's Encrypt certificates:
* EC 256 bits (SHA256withRSA)
* RSA 4096 bits (SHA256withRSA)
Without this change all the ECDSA cipher suites defined in https://github.com/discourse/discourse_docker/blob/12f501764f57c827e497eb6fb88e98f8c3c468e6/templates/web.ssl.template.yml#L22 won't work. With the new certificate all cipher suites will work and browsers like IE11 on Windows 7 and Windows 8 will work too.
**Before:**
**After:**
