-
Notifications
You must be signed in to change notification settings - Fork 103
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
IssuerKeyId criticality and unsupported implementations #263
Comments
Apologies for the regression. The reason this was changed was for consistency with OpenPGP.js, although we could theoretically change it in both. I don't think it really makes sense for this to be an option, though. Perhaps, would it be an option for you to use a fork/patch that reverts this, instead? |
yes that's a valid option as well, but it always feels a bit sketchy to use a fork of crypto lib I think, so I would like to avoid it if possible... |
We also experience the regression in Gitea's RPM package registry. Why |
PS: opened #266 not sure if we can just do that, but given it was like that for years before, I imagine we can? |
In v1.1+ (#208), the issuer key ID subpacket was made critical again (reverting #175).
RPM 4.16 (used in centos 9, fedora 34, ...) does not support it. Seems to be fixed in 4.17+.
FWIW Centos 9 EOL is set to 2027-05-31.
Is it possible to set it back to false? Does it need to be true? Can we make that optional somehow?
see:
The text was updated successfully, but these errors were encountered: