Closed GoogleCodeExporter closed 9 years ago
patch forthcoming. Like the matrixssl cert issue, this shows up in maybe ~1%
of all SSL certs on the web due to embedded systems.
Original comment by nickgsup...@gmail.com
on 15 Oct 2013 at 2:16
Sigh.
Since seconds are optional in ASN.1 UTC time, I suppose we can drop the RFC5280
requirement that utcTime MUST include seconds. Happy to take a patch.
Original comment by ekasper@google.com
on 15 Oct 2013 at 5:51
ugh
http://codereview.appspot.com/14741043
for issue #14 and #15
all of these certs are live.. and while the major browsers (+openssl) complain
about the certs being self-signed they are able to parse them, and accept them.
The other option is to to make the low level API that returns the string, and
let the caller convert.
your thoughts welcome!
nickg
Original comment by nickgsup...@gmail.com
on 16 Oct 2013 at 5:25
I think we should help the caller parse the time. Patch looks good, a few
comments on the CL.
Original comment by ekasper@google.com
on 16 Oct 2013 at 7:31
updated:
https://codereview.appspot.com/14741043/
patch set 3
(I used -rev instead of --rev for patch #2 when using upload.py)
Original comment by nickgsup...@gmail.com
on 17 Oct 2013 at 9:47
Fixed in
https://code.google.com/p/certificate-transparency/source/detail?r=8e2e1301f4ab9
bb91c8cc201c45cac0863b96b79
Thanks, Nick!
Original comment by ekasper@google.com
on 18 Oct 2013 at 2:13
Original issue reported on code.google.com by
nickgsup...@gmail.com
on 15 Oct 2013 at 12:38