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

crypto/x509: SKID generation is over full spki, rather than just the subjectPublicKey #39429

Closed
rolandshoemaker opened this issue Jun 5, 2020 · 3 comments
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@rolandshoemaker
Copy link
Member

https://go-review.googlesource.com/c/go/+/227098 introduced automatic SKID generation when one isn't provided using method (1) from RFC 5280 Section 4.2.1.2. The hash provided is over the full SPKI structure, rather than just the subjectPublicKey BIT STRING as defined, which makes it out of line with certain other implementations that assume this is how the SKID is generated.

This is unlikely to break anything major, but if the goal is to use the RFC 5280 method as defined it would make sense to stick to that construction.

@dmitshur dmitshur added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jun 5, 2020
@dmitshur dmitshur added this to the Go1.15 milestone Jun 5, 2020
@dmitshur
Copy link
Contributor

dmitshur commented Jun 5, 2020

Thanks for reporting this @rolandshoemaker.

That CL was for to fix issue #26676.

/cc @katiehockman @FiloSottile

@FiloSottile
Copy link
Contributor

Ah, good catch, looks like I got this wrong in the review even if Katie had suggested using the correct value. Better fix this for Go 1.15.

@gopherbot
Copy link

Change https://golang.org/cl/236878 mentions this issue: crypto/x509: match RFC suggested SKID generation method

@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Jun 25, 2020
@golang golang locked and limited conversation to collaborators Jun 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

5 participants