-
Notifications
You must be signed in to change notification settings - Fork 16
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
Detect usage of deprecated cipher suites #1606
Conversation
Generate changelog in
|
Just waiting on cjr 7.29.0 to publish with palantir/conjure-java-runtime#2272 for this to compile. |
tags: | ||
- name: client-name | ||
- name: client-type | ||
values: [ apache-hc5 ] |
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.
Does this provide value now? Do we run with any other client? I guess might as well leave lest we switch to something else?
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.
Ya, I figured it was best to add to all these metrics and include the static value to simplify our code.
Released 3.52.0 |
After this PR
==COMMIT_MSG==
Detect usage of deprecated cipher suites
==COMMIT_MSG==
Risks
Unlike servers, when a deprecated cipher is used, we don't have confidence that its removal would cause requests to fail. Servers ultimately choose which cipher to use, it's relatively common for java 8 servers to prefer less secure CBC ciphers over GCM due to the faster native implementation (GCM ciphers are much faster on modern jvms), however we can gauge the potential scale of impact prior to removing ciphers this way.