-
Notifications
You must be signed in to change notification settings - Fork 1.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
context: deprecate support for encrypted TLS private keys #3218
context: deprecate support for encrypted TLS private keys #3218
Conversation
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.
LGTM
@thaJeztah this PR needs to be rebased on top of |
oh! 🤦 no it's because I deprecated the
|
> 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>
1808046
to
15535d4
Compare
Codecov Report
@@ Coverage Diff @@
## master #3218 +/- ##
==========================================
- Coverage 58.58% 58.57% -0.01%
==========================================
Files 299 299
Lines 21502 21502
==========================================
- Hits 12597 12595 -2
- Misses 7983 7984 +1
- Partials 922 923 +1 |
Whoop; it's green now @silvin-lubecki ptal |
relates to #3212
follow-up to #3213
From https://go-review.googlesource.com/c/go/+/264159
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)