-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
x509_crt::key_usage is too small #192
Comments
We already fixed this issue in our internal development branch for the upcoming 2.0 branch. Thanks for your patch anyway! |
Haha, I'm glad I double-checked, because I actually didn't get to it yet, though it had been on my list for a while so I thought it was done already. I'll review your patch more carefully in the next few days. In the meanwhile, do you have any test certs? (Edit: ah, I only did the API changes, not the actual implementation, that's it.) |
Yes, here's a cert with the "decipherOnly" bit set:
|
Ok, I'm importing this in the 2.0 branch. Some nitpicking about your patch:
Here
|
I also updated |
…cy_bad_algorithm Add some negative tests for policy checks
Replace octet_string_is_eq with a constant-time implementation
It's an
unsigned char
, but the X.509 standard defines 9 flags! PolarSSL just doesn't support the "encipher only" and "decipher only" flags.It's a minor niggle.
Patch below; I'll turn it into a PR if you'd prefer, but I don't which branch to base ABI-breaking changes against (1.4 or development?)
The text was updated successfully, but these errors were encountered: