Skip to content

Comments

fix: Update policy writer to print if a rule is met but not required#5732

Open
alexw91 wants to merge 1 commit intoaws:mainfrom
alexw91:fix-policy-writer
Open

fix: Update policy writer to print if a rule is met but not required#5732
alexw91 wants to merge 1 commit intoaws:mainfrom
alexw91:fix-policy-writer

Conversation

@alexw91
Copy link
Contributor

@alexw91 alexw91 commented Feb 13, 2026

Goal

Never print Perfect Forward Secrecy: no or FIPS 140-3 (2019): no if a TLS Policy does actually meet PerfectForwardSecrecy or FIPS requirements.

Why

s2n-tls users may refer to TLS Policy snapshot files when deciding which TLS Policy to use. If a snapshot file lists a no for a given rule when it actually does meet that rule, s2n-tls users may be confused and incorrectly choose a different TLS Policy.

How

Adds an extra evaluation to the policy writer to check if a rule is met before printing no.

Callouts

None.

Testing

Manual review of TLS snapshot files.

Related

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@alexw91 alexw91 changed the title Fix TLS Policy Writer fix: Update policy writer to print if a rule is met but not required Feb 17, 2026
@alexw91 alexw91 force-pushed the fix-policy-writer branch 2 times, most recently from cfb5f46 to 67a8374 Compare February 17, 2026 22:55
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.

1 participant