-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/nginx] Specify ciphers suites and set strong ciphers #53352
Conversation
It's better to specify cipher suites to avoid having too many ciphers authorized. It allow better control of which cipher suites you use. The cipher have been choosed based on https://english.ncsc.nl/publications/publications/2021/january/19/it-security-guidelines-for-transport-layer-security-2.1 Signed-off-by: samsepi0l <contact@simpleprivacy.fr>
Signed-off-by: samsepi0l <contact@simpleprivacy.fr>
…lients that don't have AES-NI Signed-off-by: samsepi0l <contact@simpleprivacy.fr>
At the very least, we should set them up as so: ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
ssl_prefer_server_ciphers off;
ssl_conf_command Options PrioritizeChaCha; Based on:
These cipher suites might be better for everyone use. |
Hi @d4rklynk, Thank you for your contribution and sorry for the delay. Please let us review and test the changes before merging them. Thanks |
Hi @d4rklynk, I just reviewed your changes and proposed some changes according to the information you provided. Could you please review them and ping me here in this main thread so I get notified? Thanks |
Hi @jotamartos , sorry, I don't see the changes that you proposed on my end. Could you confirm that you submitted your suggestions? |
Yes, I added the comment and I can see it as well. The changes I proposed were basically these ones
|
bitnami/nginx/1.25/debian-11/rootfs/opt/bitnami/nginx/conf/nginx.conf
Outdated
Show resolved
Hide resolved
So sorry about the review submission 😅 I thought I clicked on it. |
…nx.conf Co-authored-by: Juan José Martos <jotamartos@gmail.com> Signed-off-by: samsepi0l <contact@samsepi0l.dev>
LGTM, Just keep in mind that DHE is weak under somes circumstances -> https://ciphersuite.info/cs/TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256/ Is it relevant to add strong ciphers commented out ? (in case someones needs it) |
I think that may confuse users. If the user knows what he's configuring, he'll set the list of ciphers he really wants to use but if he doesn't have enough experience with NGINX, he will probably end up enabling/disabling ciphers he does/doesn't really need. Let me migrate this information to our systems and will merge this PR after that. Thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this contribution!
It's better to specify cipher suites to avoid having too many ciphers authorized.
It allows better control of which cipher suites you use.
Only strong ciphers have been chosen.
The cipher have been choosed based on https://english.ncsc.nl/publications/publications/2021/january/19/it-security-guidelines-for-transport-layer-security-2.1
Only a few very very old version of somes OSes will not work (like OX 10.10 that ended 6 years ago).
You can check a handshake simulation example here with these ciphers.