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
after opening my V 1.3.1 DB with version 2.10 the DB was converted. When signing the first CSR there was an error mesage: "Failed to retrieve unique random serial". In the next try there was no error message and the certificate was generated. But with a serial already in the database.
Best regards,
Daniel
The text was updated successfully, but these errors were encountered:
Did the certificates with identical serials have the same issuer?
It is only necessary for certificates issued by the same issuer to have unique serials.
The issue is caused by to narrow random serials (8 bit). It should be 64 bit.
Yes, the new certificate was signed by the same issuer. The serial was a two digit hex. I noticed the problem because this serial was on the crl already.
Is the Serial also listed in the "CA -> Manage revocations" context menu of the CA?
Because serials on the CRL are also checked and refused when generating a new random serial.
But therefore they must be known by XCA.
I checked this functionality right know and seems to work.
Hi,
after opening my V 1.3.1 DB with version 2.10 the DB was converted. When signing the first CSR there was an error mesage: "Failed to retrieve unique random serial". In the next try there was no error message and the certificate was generated. But with a serial already in the database.
Best regards,
Daniel
The text was updated successfully, but these errors were encountered: