Repository navigation
[skip-ci] docs: correct wildcard description for allowed tunnel CNs - #8274
Merged
Merged
Conversation
Assisted-by: reasoning/desy-assistant
Updated the configuration message to reflect the new domain name for CN matching.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Suggested documentation update for 4945b39 ("LocationManager: check for allowed CN before opening tunnel"). Corrects the description of the wildcard syntax for the new allowed-CN allowlist: the implementation and its unit tests support leading, infix and trailing
*, not only trailing wildcards. Also documents that a line is only a comment when#is the first non-blank character. AI-generated — please review for accuracy before merging.