-
Notifications
You must be signed in to change notification settings - Fork 4.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
docs: Update cipher suites documentation #20697
Conversation
Pinging @elastic/integrations-services (Team:Services) |
Pinging @elastic/obs-docs (Team:Docs) |
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!
Chatted with @andrewvc about adding the following ciphers to the documentation: beats/libbeat/common/transport/tlscommon/types.go Lines 69 to 71 in 5f42d21
We agreed they should be added, but now I'm noticing that TLS 1.3 cipher suites are not individually configurable in Go... So I don't think they need to be added after all. |
Bump @elastic/integrations-services. Can I get a review on this, please? I'm specifically interested in the two open questions in the description. |
@bmorelli25 I added the cipher suites there not so much to make them configurable but so that inverse lookups would work (we flip that map around and use it for inverse lookups). We use these inverse lookups to report the cipher suite used in heartbeat data. If they aren't configurable maybe the docs should reflect that, but the code should stay. |
Neat. The docs say "Note that TLS 1.3 cipher suites are not individually configurable in Go, so they are not included in this list.", so I think we're good then! Thanks, Andrew. EDIT: Sorry, I reread and realize I wasn't clear in my comment above. I wasn't suggesting we remove them from the code, just that we exclude them from the docs. |
…ne-2.0 * upstream/master: (87 commits) [packaging] Normalise GCP bucket folder structure (elastic#20903) [Metricbeat] Add billing metricset into googlecloud module (elastic#20812) Include python docs in devguide index (elastic#20917) Avoid generating incomplete configurations in autodiscover (elastic#20898) Improve docs of leaderelection configuration (elastic#20601) Document how to set the ES host and Kibana URLs in Ingest Manager (elastic#20874) docs: Update beats for APM (elastic#20881) Adding cborbeat to community beats (elastic#20884) Bump kibana version to 7.9.0 in x-pack/metricbeat (elastic#20899) Kubernetes state_daemonset metricset for Metricbeat (elastic#20649) [Filebeat][zeek] Add new x509 fields to zeek (elastic#20867) [Filebeat][Gsuite] Add note about admin in gsuite docs (elastic#20855) Ensure kind cluster has RFC1123 compliant name (elastic#20627) Setup python paths in test runner configuration (elastic#20832) docs: Add `processor.event` info to Logstash output (elastic#20721) docs: update cipher suites (elastic#20697) [ECS] Update ecs to 1.6.0 (elastic#20792) Fix path in hits docs (elastic#20447) Update filebeat azure module documentation (elastic#20815) Remove duplicate ListGroupsForUsers in aws/cloudtrail (elastic#20788) ...
What does this PR do?
This PR:
cipher_suites
documentation to better display TLS version compatibility.Why is it important?
This content previously only existed in the APM Server's output (server ←→ es) documentation.
Open questions
beats/libbeat/common/transport/tlscommon/types.go
Lines 69 to 71 in 5f42d21
Related issues
For elastic/apm-server#4002.
Screenshots