Skip to content
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

util: Use TLSv1.2 as minimum TLS version by default #36037

Merged
merged 12 commits into from
Jan 4, 2024

Conversation

dveeden
Copy link
Contributor

@dveeden dveeden commented Jul 8, 2022

What problem does this PR solve?

Issue Number: close #36036

Problem Summary:

What is changed and how it works?

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

The minimum TLS version has been changed from TLSv1.1 to TLSv1.2 to comply with IETF RFC 8996.

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Jul 8, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • hawkingrei

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 8, 2022
@sre-bot
Copy link
Contributor

sre-bot commented Jul 8, 2022

@dveeden
Copy link
Contributor Author

dveeden commented Jul 12, 2022

/cc @likzn @hawkingrei @zhangyangyu

@ti-chi-bot ti-chi-bot requested a review from hawkingrei July 12, 2022 06:23
@ti-chi-bot
Copy link
Member

@dveeden: GitHub didn't allow me to request PR reviews from the following users: likzn.

Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @likzn @hawkingrei @zhangyangyu

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ti-chi-bot ti-chi-bot requested a review from zhangyangyu July 12, 2022 06:23
@zhangyangyu
Copy link
Member

I think this is not a simple one line change. It might affect some users still using TLSv1.1(both conscious & unconscious). We need to see how the product managers think.

@xhebox xhebox added the compatibility-breaker Violation of forwards/backwards compatibility in a design-time piece. label Jul 13, 2022
@dveeden
Copy link
Contributor Author

dveeden commented Jul 13, 2022

I think this is not a simple one line change. It might affect some users still using TLSv1.1(both conscious & unconscious). We need to see how the product managers think.

Yes I agree.

If people use very old clients that use YaSSL they won't be able to use TLSv1.2 or newer.
(see also: https://dev.mysql.com/doc/refman/5.7/en/ssl-libraries.html )

However this should only be merged into master and not be backported. So this won't affect users of TiDB v6.1.x or older.

This is only changing the default, so people can change the config to allow TLSv1.1 if needed.

This will improve security and may also be beneficial for compliance with various regulations.

@dveeden
Copy link
Contributor Author

dveeden commented Jul 13, 2022

This is how MySQL handles this: (source: https://dev.mysql.com/doc/refman/8.0/en/encrypted-connection-protocols-ciphers.html )

image

@dveeden
Copy link
Contributor Author

dveeden commented Jul 13, 2022

/label security

@ti-chi-bot ti-chi-bot added the security Everything related with security label Jul 13, 2022
@lulukelu
Copy link

lulukelu commented Aug 9, 2022

Customers can choose TLS 1.1, 1.2, 1.3 versions, the default is to configure TLS 1.2, but does not support TLS1.0?

@dveeden
Copy link
Contributor Author

dveeden commented Aug 9, 2022

Customers can choose TLS 1.1, 1.2, 1.3 versions, the default is to configure TLS 1.2, but does not support TLS1.0?

By default TiDB supports TLSv1.1, 1.2 and 1.3. It can be configured to support TLSv1.0.

This change would change the default to only support TLSv1.2 and TLSv1.3.

@dveeden
Copy link
Contributor Author

dveeden commented Mar 7, 2023

@lulukelu could you suggest reviewers for this PR?

@lulukelu lulukelu requested review from ljun0712 and lulukelu and removed request for ljun0712 March 8, 2023 23:05
@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Nov 23, 2023
@dveeden
Copy link
Contributor Author

dveeden commented Nov 23, 2023

/hold

I'd like to make sure @bb7133 is ok with merging this.

@ti-chi-bot ti-chi-bot bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 23, 2023
@dveeden dveeden added type/compatibility compatibility-mysql8 This is a compatibility issue with MySQL 8.0(but NOT 5.7) labels Dec 5, 2023
@dveeden dveeden mentioned this pull request Dec 5, 2023
70 tasks
@dveeden dveeden removed type/compatibility compatibility-mysql8 This is a compatibility issue with MySQL 8.0(but NOT 5.7) labels Dec 5, 2023
@dveeden
Copy link
Contributor Author

dveeden commented Dec 11, 2023

/unhold

@ti-chi-bot ti-chi-bot bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 11, 2023
Copy link

ti-chi-bot bot commented Dec 11, 2023

@ljun0712: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@dveeden
Copy link
Contributor Author

dveeden commented Dec 12, 2023

/hold

@ti-chi-bot ti-chi-bot bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 12, 2023
Copy link
Member

@bb7133 bb7133 left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link

ti-chi-bot bot commented Jan 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bb7133, CbcWestwolf, hawkingrei, ljun0712, lulukelu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [CbcWestwolf,bb7133,hawkingrei]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jan 4, 2024
Copy link

ti-chi-bot bot commented Jan 4, 2024

[LGTM Timeline notifier]

Timeline:

  • 2023-11-23 10:07:32.218097971 +0000 UTC m=+485280.883324151: ☑️ agreed by CbcWestwolf.
  • 2024-01-04 18:19:00.117160584 +0000 UTC m=+2367431.154387526: ☑️ agreed by bb7133.

@bb7133
Copy link
Member

bb7133 commented Jan 4, 2024

/unhold

@ti-chi-bot ti-chi-bot bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 4, 2024
@ti-chi-bot ti-chi-bot bot merged commit 3ced975 into pingcap:master Jan 4, 2024
10 of 11 checks passed
@tiancaiamao tiancaiamao mentioned this pull request Jan 12, 2024
13 tasks
AilinKid pushed a commit to AilinKid/tidb that referenced this pull request Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved compatibility-breaker Violation of forwards/backwards compatibility in a design-time piece. lgtm ok-to-test Indicates a PR is ready to be tested. release-note Denotes a PR that will be considered when it comes time to generate release notes. security Everything related with security size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. status/LGT1 Indicates that a PR has LGTM 1.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The minimum TLS version should comply with IETF RFC 8996
10 participants