Skip to content
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

SKI is now not recommended. #788

Closed
wants to merge 1 commit into from

Conversation

baloo
Copy link
Contributor

@baloo baloo commented Jan 22, 2024

Ballot SC62 appears to have marked Subject Key Identifier as NOT RECOMMENDED.

https://cabforum.org/2023/03/17/ballot-sc62v2-certificate-profiles-update/

See section 7.1.2.7.6 Subscriber Certificate Extensions of the BR: https://cabforum.org/wp-content/uploads/CA-Browser-Forum-TLS-BR-2.0.2.pdf#page=79

I believe zlint should stop issuing warnings for certificates issued after SC62 was effective.

Ballot SC62 appears to have marked Subject Key Identifier as NOT
RECOMMENDED.

https://cabforum.org/2023/03/17/ballot-sc62v2-certificate-profiles-update/

See section 7.1.2.7.6 Subscriber Certificate Extensions of the BR:
https://cabforum.org/wp-content/uploads/CA-Browser-Forum-TLS-BR-2.0.2.pdf#page=79

I believe zlint should stop issuing warnings for certificates issued
after SC62 was effective.
@baloo
Copy link
Contributor Author

baloo commented Jan 22, 2024

Fair warning:
I've never contributed here, nor interacted with the CABF before. Please take this as a suggestion and use of grains of salt are highly suggested.

@baloo baloo changed the title SKI is now NOT recommended. SKI is now not recommended. Jan 22, 2024
@XolphinMartijn
Copy link
Contributor

Issue #749 ties into this. I'm not sure the proposed solution here is optional.

The linter source is lint.RFC5280. That source still says the same about this SHOULD requirement.

SC62 went against RFC5280 in this regard. It seems to me like it's a case where the RFC5280 lint should still show a warning if the SKI is not present, where-as a similar lint for Source CABFBR, should print a warning is it is present.

Anyone linting, could then exclude one of the two, depending on which requirement they'd like to follow more strictly

@baloo
Copy link
Contributor Author

baloo commented Jan 22, 2024

I missed #749. closing this and following up there.

@baloo baloo closed this Jan 22, 2024
@baloo baloo deleted the baloo/ski-end-certificates branch January 22, 2024 17:09
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.

2 participants