Skip to content
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

ncm-metaconfig: nginx default ssl settings outdated #1717

Open
wdpypere opened this issue Sep 14, 2024 · 2 comments
Open

ncm-metaconfig: nginx default ssl settings outdated #1717

wdpypere opened this issue Sep 14, 2024 · 2 comments

Comments

@wdpypere
Copy link
Contributor

Looking at the nginx schema I see following defaults:

    "ciphersuite" : cipherstring[] = list("TLSv1")
    "protocol" : sslprotocol[] = list("TLSv1", "TLSv1.1", "TLSv1.2", "TLSv1.3")

This is quite weak, and outdated. Do we regard it as our responsibility to provide secure defaults? Otherwise I would change these to:

    "ciphersuite" : cipherstring[] = list("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", "DHE-RSA-CHACHA20-POLY1305")
    "protocol" : sslprotocol[] = list("TLSv1.2", "TLSv1.3")

which would work on el8 (nginx 1.17) and beyond. Maybe lower as well but I don't have a el7 machine to test.

@ned21
Copy link
Contributor

ned21 commented Sep 15, 2024

+1 to not shipping weak defaults. I think there's a couple of options:

  1. Remove the default value, let users experience a compile error and choose their own value.
  2. Adjust the default value as you suggest, at the risk of breaking EL7 and storing up problems for future maintainers.

Both options are backwards incompatible, the first leads to a template compile error with trivial fix, the second will likely work seamlessly for people but carries the risk of breaking a deployed app somewhere.

@jrha
Copy link
Member

jrha commented Sep 16, 2024

My vote would be for 2️⃣ with an appropriate call-out in the release notes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants