Server protects yaml as well as yml#2182
Merged
Merged
Conversation
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
1 participant
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.
Category
Bugfix / Security
Overview
There was a bug, whereby: if you use OIDC for auth, and update your config locations via custom env vars to use
.yamlinstead of.ymlthen auth will not work.Note that while this was opened as a security advisory, and I will publish the advisory or transparency and to trigger updates, this issue doesn't actually have any way to exploit, and so is a no-op.
Issue Number
Thanks @huslayer826 for reporting this, in GHSA-7v4p-jf7g-wpg7!