-
Notifications
You must be signed in to change notification settings - Fork 1.6k
ValueError: time data '20160812233616+0200' does not match format '%Y%m%d%H%M%SZ' #3086
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
Comments
$ dumpasn1 -hh time.der 0 warnings, 1 error. Is it possible that your CRL is wrong? |
OpenSSL seems happy:
|
Huh. https://tools.ietf.org/html/rfc5280#section-4.1.2.5.1 Re-opening this on the Vault side, although I'm unsure if it's a Vault issue or an issue in Go. It'd be nice if pyca would accept non-zulu values but that suggests that it doesn't need to. |
Thanks for the report! I'm reluctant to parse values like this since it will hide bugs that should be fixed (as it appears it was in this case! Yay!). I reserve the right to pragmatically change my mind if a very large system forces us to be bug compatible in the future though. 😄 |
As an FYI, I also opened golang/go#16686 |
Python version: CPython 3.5.1
Operating system: OS X El Capitan 10.11.6
cryptography.version: 1.4
openssl.openssl_version_text(): OpenSSL 1.0.2h 3 May 2016
I'm using Vault's PKI backend for issuing certificates. I revoked one certificate. My CRL:
seems fine.
The following program:
throws this message:
The text was updated successfully, but these errors were encountered: