New answers tagged certificates
Cryptographically speaking, a digital signature provides the property of non-repudiation -- the signer cannot deny signing once signed. So, you either have to keep the unsigned version if you can't strip the signature from the document, or sign another document invalidating the previous signature if the previous document has been released.
From RFC 2985: The challengePassword attribute type specifies a password by which an entity may request certificate revocation. The interpretation of challenge passwords is intended to be specified by certificate issuers etc; no particular interpretation is required. This has also come up over at Information Security Stackexchange with the TL;DR ...
Building such a table would be very difficult, because certificate-sizes depend on a lot of (variable-sized) things, including but not limited to: usage constraints signatures public keys URLs to CRLs and OCSP-servers Name, location and other identifiers of the key-holder Name, location and other identifiers of the issuing CA However, you can estimate ...
Top 50 recent answers are included