Hot answers tagged public-key-infrastructure
6
According to your comments to other answers, you actually want to
sign a pdf file with [your] certificate, then have this signature saved and appended to the pdf [you]'ve just signed.
(BTW, you sign with the private key associated with the public key in your certificate, not with the certificate itself, but that's a detail.)
I assume you want to ...
6
To quote from pqcrypto.org: "Imagine that it's fifteen years from now. Somebody announces that he's built a large quantum computer. RSA is dead. DSA is dead. Elliptic curves, hyperelliptic curves, class groups, whatever, dead, dead, dead." Worth a visit to their site to understand what crypto looks like after the (hypothetical) success of quantum computing.
5
When the machine says that "you have the private key corresponding to this certificate", then this means that you have the private key which corresponds to the certificate, not that the certificate itself contains the private key.
Asymmetric keys come in pairs: the public key and the private key. They are mathematically linked to each other, but rebuilding ...
3
A "Key Escrow" is used in cases where a third-party needs access to encrypted data, as defined by law (so if you get a court order to decrypt data), while a "Recovery Agent" is someone who is permitted to decrypt another user's data in case of emergency and has a key that can accomplish the decryption.
So in effect, the key escrow is someone who holds the ...
2
This protocol is vulnerable to a replay attack.
In common notation
A -> I_B: {m}_PK(B)
I_A -> B: {m}_PK(B)
I_A -> B: {m}_PK(B)
If m was a message saying loan me $10 and B was a little naive ...
This protocol is also vulnerable to message reordering attacks e.g.
A -> I_B: {m}_PK(B)
A -> I_B: {m'}_PK(B)
I_A -> B: {m'}_PK(B)
I_A -> B: ...
1
An end-entity certificate is a certificate which is not used to validate signatures on other certificates, i.e. a certificate which does not contain a CA public key (its Basic Constraints extension is absent, or contains a cA flag with value FALSE). It is called "end-entity" because it appears, necessarily, at the end of a certificate path.
A CRL issuer ...
1
If you want to sign a PDF, most PDF writers, and some versions of the reader-only will have a built in mechanism for signing, and some even for timestamping. It will ask you to provide your certificate file and then it will apply the digital signature into the file. PDFs in particular have this mechanism built into the format, but it is also possible to sign ...
1
Your question is really two different questions. A certificate only needs to be signed by another certificate if there needs to be a chain of trust. For example, a root CA will sign the certificates they issue so that anyone trying to verify the certificate will know that it is trusted by the CA. You can do this kind of chaining with any certificate that ...
1
A certificate always contains a signature, but on itself, not on some PDF document. This signature is an integral part of the certificate and has been computed by the CA which issued the certificate; this is by verifying this signature that any software can gain some trust in the contents of the certificate. All of this happens independently of any PDF file, ...
1
As the certificate is registered to you and fields completed with your details, the certificate is your digital signature. You don't add a digital signature to the certificate.
You need a certificate to be issued by a CA (which you could create). Then add the certificate to your trusted certs (if self-signed or not from an standard recognised CA). When you ...
Only top voted, non community-wiki answers of a minimum length are eligible
