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.

Sign up for GitHub

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

Jump to bottom

update doc of require_secure_transport #15587

Merged
merged 5 commits into from
Dec 7, 2023
Merged

update doc of require_secure_transport #15587

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
c3965e5
Add temp.md
qiancai Dec 1, 2023
1fa00f8
Delete temp.md
qiancai Dec 1, 2023
5f66683
Update system-variables.md
qiancai Dec 1, 2023
5ee54e0
Update system-variables.md
qiancai Dec 5, 2023
3bf1d1c
Update system-variables.md
qiancai Dec 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions system-variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -546,6 +546,7 @@ mysql> SHOW GLOBAL VARIABLES LIKE 'max_prepared_stmt_count';

- Setting this variable to `ON` requires you to connect to TiDB from a session that has TLS enabled. This helps prevent lock-out scenarios when TLS is not configured correctly.
- This setting was previously a `tidb.toml` option (`security.require-secure-transport`), but changed to a system variable starting from TiDB v6.1.0.
- For v6.5.6 or later v6.5.x releases, when Security Enhanced Mode (SEM) is enabled, setting this variable to `ON` is prohibited to avoid potential connectivity issues for users.
qiancai marked this conversation as resolved.
Show resolved Hide resolved

### skip_name_resolve <span class="version-mark">New in v5.2.0</span>

Expand Down
Loading