Skip to content

fips: clarify how Envoy follows the fips update stream#43523

Open
ggreenway wants to merge 1 commit intoenvoyproxy:mainfrom
ggreenway:fips-policy
Open

fips: clarify how Envoy follows the fips update stream#43523
ggreenway wants to merge 1 commit intoenvoyproxy:mainfrom
ggreenway:fips-policy

Conversation

@ggreenway
Copy link
Member

No description provided.

Signed-off-by: Greg Greenway <ggreenway@apple.com>
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.

Copy link
Member

Choose a reason for hiding this comment

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

I'd just add something like "This is in accordance with Envoy's policy for updating stable branches.", linking to RELEASES.md.

Copy link
Member

@phlax phlax left a comment

Choose a reason for hiding this comment

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

lgtm, thanks @ggreenway

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants