fips: clarify how Envoy follows the fips update stream#43523
Merged
Conversation
Signed-off-by: Greg Greenway <ggreenway@apple.com>
jwendell
reviewed
Feb 17, 2026
| of FIPS BoringSSL code. When an Envoy stable release branch is made, the BoringSSL FIPS version used | ||
| will be compatible with the Update Stream policy, and that version (and associated build tool versions) will | ||
| not be changed on the release branch unless a bug or security vulnerability which affects Envoy is reported. | ||
|
|
Member
There was a problem hiding this comment.
I'd just add something like "This is in accordance with Envoy's policy for updating stable branches.", linking to RELEASES.md.
Member
|
lets land this - we can iterate if we need to |
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
3 participants
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.
No description provided.