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

tlsconfig: deprecate support for encrypted TLS private keys #93

Merged
merged 1 commit into from
Nov 10, 2023

Conversation

thaJeztah
Copy link
Member

relates to docker/cli#3212

Legacy PEM encryption as specified in RFC 1423 is insecure by design. Since
it does not authenticate the ciphertext, it is vulnerable to padding oracle
attacks that can let an attacker recover the plaintext

From https://go-review.googlesource.com/c/go/+/264159

It's unfortunate that we don't implement PKCS#8 encryption so we can't
recommend an alternative but PEM encryption is so broken that it's worth
deprecating outright.

@thaJeztah thaJeztah force-pushed the deprecate_encrypted_tls branch 2 times, most recently from fe20047 to 080f0c3 Compare July 27, 2021 19:21
> Legacy PEM encryption as specified in RFC 1423 is insecure by design. Since
> it does not authenticate the ciphertext, it is vulnerable to padding oracle
> attacks that can let an attacker recover the plaintext

From https://go-review.googlesource.com/c/go/+/264159

> It's unfortunate that we don't implement PKCS#8 encryption so we can't
> recommend an alternative but PEM encryption is so broken that it's worth
> deprecating outright.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah thaJeztah force-pushed the deprecate_encrypted_tls branch from 080f0c3 to e1b2673 Compare November 10, 2023 19:47
@thaJeztah thaJeztah merged commit b2bece1 into docker:master Nov 10, 2023
13 checks passed
@thaJeztah thaJeztah deleted the deprecate_encrypted_tls branch November 10, 2023 19:56
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

Successfully merging this pull request may close these issues.

2 participants