docs: add signature algorithms reference #47976
Conversation
github-actions
bot
requested review from
mmcallister,
r0mant,
xinding33 and
zmb3
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
nklaassen
added
the
no-changelog
|
🤖 Vercel preview here: https://docs-1ltuyri20-goteleport.vercel.app/docs/ver/preview |
| Historically, every Teleport-issued certificate was signed by a 2048-bit RSA key. | ||
| RSA is one of the oldest and most well-known asymmetric cryptography algorithms. | ||
| While it is still considered secure (as long as your keys are large enough), | ||
| modern alternatives based on Elliptic-Curve Cryptography offer much better | ||
| performance with smaller keys and better security. |
There was a problem hiding this comment.
Since the algorithms are configurable, I would use this paragraph to describe when a user would want to configure the algorithm used, i.e., when they would want to continue reading in order to choose an algorithm to configure (answering the question, "Does this guide apply to my use case?").
There was a problem hiding this comment.
edited the full intro to:
The Teleport Auth Service issues SSH and TLS certificates to users and hosts that allow all connections to be authenticated, authorized, and encrypted. This page describes the cryptographic signature algorithms used to sign each kind of certificate issued by Teleport.
Continue reading to learn how to:
- configure a Teleport cluster created before Teleport 17 to use fast and secure elliptic-curve keys
- configure your cluster to use FIPS-compatible signature algorithms
- configure your cluster to use signature algorithms compatible with your HSM or KMS.
public-teleport-github-review-bot
bot
removed request for
r0mant,
mmcallister and
xinding33
|
🤖 Vercel preview here: https://docs-clneyjykg-goteleport.vercel.app/docs/ver/preview |
Backport #47976 to branch/v17
Backports #47976 * docs: add signature algorithms reference * edits
This PR adds documentation for the Modern Signature Algorithms feature being release in v17.0.0.
The issue is tracked here and the RFD is here.