-
Notifications
You must be signed in to change notification settings - Fork 690
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
internal/dag: reject certificates with CN or SubjectAltName
Fixes #1965 During cache insertion reject certificates which lack a Subject CommonName (CN) or SubjectAltName extension. This PR uncovered that, well basically, all our TLS fixtures don't fit this requirement which is extra sadface and thus this PR contains replacement fixtures for all the previous ones. This PR also adds a unit test for dag.isValidSecret as we are likely to continue to add to this function as further validation edge cases are uncovered. This necessitated a small addition to the internal/assert comparator logic to be able to compare error values. Signed-off-by: Dave Cheney <[email protected]>
- Loading branch information
1 parent
a1138bc
commit 11d5179
Showing
7 changed files
with
384 additions
and
395 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains 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
This file contains 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
Oops, something went wrong.