Changes between Version 1 and Version 2 of Ticket #46596, comment 2


Ignore:
Timestamp:
Jan 18, 2015, 10:41:20 AM (9 years ago)
Author:
mouse07410 (Mouse)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #46596, comment 2

    v1 v2  
    1818
    1919I think the cause of this problem is somewhere in the certificate decoding piece, where either an explicit ASN.1 NULL gets added when it shouldn't, or the code forgets to add it when it should.
     20'''''Correction''': after checking the actual certificate ASN.1 encoding, I found that indeed in all places but one, signature algorithm parameters part is encoded as ASN.1 NULL; and in one place the parameters part is just not present (thus decoded as null pointer). I still maintain that the two are equal.'' :)
    2021
    2122The following is a reasonable secure workaround, until somebody figures why certificate parsing is screwed up: