-
Notifications
You must be signed in to change notification settings - Fork 687
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
v5.2.2: Update TLS docs #6323
v5.2.2: Update TLS docs #6323
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
The list on https://pkg.go.dev/crypto/tls#pkg-constants doesn't match exactly with the list on https://docs.pingcap.com/tidb/stable/enable-tls-between-clients-and-servers#supported-tls-versions-key-exchange-protocols-and-encryption-algorithms Should it match exactly? |
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. For the chinese translation you might want to ask @s3nt3 for translation or review, because the usage of some of the language is very specific.
For v5.2.x additions, could you please add the description: "Since v5.2.2, ...."? |
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
@dveeden Any update? |
@TomShawn added some text about |
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
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 28aeb2a
|
In response to a cherrypick label: new pull request created: #6646. |
|
||
If the certificate parameters are correct, TiDB outputs `secure connection is enabled` when started; otherwise, it outputs `secure connection is NOT ENABLED`. | ||
|
||
For TiDB versions earlier than v5.2.0, you can use `mysql_ssl_rsa_setup --datadir=./certs` to generate certficates. The `mysql_ssal_rsa_setup` tool is a part of MySQL Server. |
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.
There seems to be a mistake: mysql_ssal_rsa_setup should be changed to mysql_ssl_rsa_setup.
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.
fixed in b9ce3fe.
What is changed, added or deleted? (Required)
Update TLS docs with:
mysql_ssl_rsa_setup
as this is replaced with AutoTLSWhich TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Closes #6387
Including this:
Not including this as it doesn't apply to v5.2: