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

ciphersuites restriction does not prevent TLS_AES_128_GCM_SHA256 from being accepted #152

Open
phrankemp opened this issue Oct 16, 2023 · 1 comment

Comments

@phrankemp
Copy link

Arch: s390x, Version 2.8.3

I have minimumtls set to "tls1.3" and am restricting ciphersuites to TLS_AES_256_GCM_SHA384. This is confirmed in the log on startup.

No matter how I restrict the ciphersuites, I can always connect successfully from openssl using the TLS_AES_128_GCM_SHA256 cipher.
Other ciphers are restricted properly.

Any thoughts as to why this might be happening?

Thanks in advance...

@milosgajdos
Copy link
Member

I'd encourage you to open this question in https://github.com/distribution/distribution

Whilst this repo still tracks releases of the official image, you'll get better luck in the code repository that.

It'd be great if you provided the exact configuration file that could help the maintainers to investigate.

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

No branches or pull requests

2 participants