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
I am using version 0.1.7 of the wolfssl Command Line Utility. Linked to wolfSSL version 5.7.6
Description
Hello Developer,
I have a CRL file, and its CRL number field is 1340261524025379168094198301688384645909778198. According to RFC5280, the CRL parser must be able to handle CRL numerical values up to 20 bytes, which corresponds to a maximum decimal integer of 49 digits. However, the CRL number field above is a 46-digit decimal integer. The result from parsing with wolfCLU is 1318915862. So, is this a bug?
Reproduction steps
wolfssl crl -inform der -in crl_file_serial.der -text
Contact Details
No response
Version
I am using version 0.1.7 of the wolfssl Command Line Utility. Linked to wolfSSL version 5.7.6
Description
Hello Developer,
I have a CRL file, and its CRL number field is 1340261524025379168094198301688384645909778198. According to RFC5280, the CRL parser must be able to handle CRL numerical values up to 20 bytes, which corresponds to a maximum decimal integer of 49 digits. However, the CRL number field above is a 46-digit decimal integer. The result from parsing with wolfCLU is 1318915862. So, is this a bug?
Reproduction steps
wolfssl crl -inform der -in crl_file_serial.der -text
crl_file_serial.zip
Relevant log output
The text was updated successfully, but these errors were encountered: