Skip to content

feat(om2): recommend TLS 1.3 while keeping TLS 1.2 as minimum#2925

Merged
bwplotka merged 2 commits intomainfrom
krajo/om2-tls13
Mar 30, 2026
Merged

feat(om2): recommend TLS 1.3 while keeping TLS 1.2 as minimum#2925
bwplotka merged 2 commits intomainfrom
krajo/om2-tls13

Conversation

@krajorama
Copy link
Copy Markdown
Member

Summary

  • Adds a SHOULD for TLS 1.3 or later alongside the existing TLS 1.2 minimum requirement
  • TLS 1.3 (RFC 8446, 2018) is the current industry standard with better security and performance
  • TLS 1.2 remains as the minimum floor for backwards compatibility
  • Applies to both Protocol Negotiation and Security sections

Test plan

  • Verify the change renders correctly in the docs site

Signed-off-by: György Krajcsovits gyorgy.krajcsovits@grafana.com

🤖 Coded with Claude Sonnet 4.6. Generated with Claude Code

TLS 1.3 (RFC 8446) is the current industry standard. Keep TLS 1.2 as
the minimum for compatibility but add a SHOULD for TLS 1.3.

Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>
Coded with Claude Sonnet 4.6.
Co-authored-by: David Ashpole <dashpole@google.com>
Signed-off-by: George Krajcsovits <krajorama@users.noreply.github.com>
Copy link
Copy Markdown
Member

@bwplotka bwplotka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏽
Thanks!

@bwplotka bwplotka merged commit 3d727c5 into main Mar 30, 2026
7 checks passed
@bwplotka bwplotka deleted the krajo/om2-tls13 branch March 30, 2026 13:15
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.

3 participants