-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limit scope for cn checking in SAN #825
Conversation
This reverts commit 6c23670.
util: gtld_map autopull updates for 2021-10-21T07:25:20 UTC
for _, commonName := range name.CommonNames { | ||
if util.IsMailboxAddress(commonName) { | ||
mailboxAddresses = append(mailboxAddresses, commonName) | ||
if includeCN { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if includeCN { | |
if len(name.EmailAddress) == 0 { |
This would cover more scenario's and doesn't require additional function parameters.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would not that, probably very unlikely, produce some false positives? E.g. for a sponsor-validated certificate with a subjectDN featuring a CN which has a pseudonym with a @ character and no emailAddress RDN in subject.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That might be possible indeed.
Agreed |
This PR addresses issues of discussion in PR #809