You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello Developer:
I have a CRL file, and the "O" field in its issuer section contains an escape character. The value of the "O" field is 'VeriSign\'. When I use Bouncy Castle 1.80 to parse this CRL file, Bouncy Castle 1.80 interprets the "O" field as 'VeriSign\\'. However, when I open the CRL file as a .crl file, the "O" field in the issuer section shows as 'VeriSign\'.
Therefore, I suspect that the handling of the escape character '\\' by Bouncy Castle 1.80 may not be entirely reasonable.
Hello Developer:
I have a CRL file, and the "O" field in its issuer section contains an escape character. The value of the "O" field is 'VeriSign\'. When I use Bouncy Castle 1.80 to parse this CRL file, Bouncy Castle 1.80 interprets the "O" field as 'VeriSign\\'. However, when I open the CRL file as a .crl file, the "O" field in the issuer section shows as 'VeriSign\'.
Therefore, I suspect that the handling of the escape character '\\' by Bouncy Castle 1.80 may not be entirely reasonable.
Code:
Actual results:
The issuer field is parsed as Issuer: OU=Class 3 Public Primary Certification Authority,CN=test,O=VeriSign\\,L=test,ST=test,C=US.
Test case:
crl_file_.zip
The text was updated successfully, but these errors were encountered: