Timeline for Crypto++ RSA - Encrypt and sign with the same key pair
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 17, 2016 at 20:11 | comment | added | Mok-Kong Shen | But "a pair" means 2 pieces, isn't it? So that the receiver can read an encrypted message, the sender has to use receiver's public key. If the sender has to sign anything, he has to use his private key. So that the receiver can verify sender's signature, he has to use sender's public key. So with the requirements of your OP, there are a total of 3 keys involved, not 2 or just 1 (in the common case of no signature). There are certainly diverse ways to achieve the same goal, One way I use is in Example 3S of s13.zetaboards.com/Crypto/topic/7234475/1/ which employs RSA alone (nothing else). | |
| May 17, 2016 at 16:32 | comment | added | galinette | At the heart of RSA, a key is neither public nor private, there are just to related keys (ie a key pair). It's the use which makes them public or private. For encryption, the receiver key is private. For signing, the sender key is private. If you use the same keys for a signed encrypted message, both should not be disclosed and are to be considered private. This is why I'm using the term "key pair" instead of "public" and "private" keys. | |
| May 17, 2016 at 15:46 | comment | added | Mok-Kong Shen | I don't yet understand what you mean by "a single RSA key pair, with a key for A and a key for B" (I use B for your Bn). Do you mean the pair (e,n) and (d,n), with the same n, of A, i.e. the public and private key of A respectively, and B doesn't have any keys of its own or what? Wouldn't A need B's public key in order to send something encrypted to it at all? | |
| May 17, 2016 at 15:45 | comment | added | SEJPM | Re 2: Given any standard representation of the private key it is trivial to recover the public key and thus it wouldn't make sense to hide it here. Additionally it would make the user experience much worse because you usually generate and store a private key to then send someone a public key. | |
| May 17, 2016 at 13:17 | history | edited | StackzOfZtuff | CC BY-SA 3.0 | added 15 characters in body |
| May 17, 2016 at 10:50 | answer | added | Lucas Kauffman | timeline score: 2 | |
| May 17, 2016 at 10:46 | history | edited | galinette | CC BY-SA 3.0 | added 113 characters in body |
| May 17, 2016 at 10:35 | review | First posts | |||
| May 17, 2016 at 10:41 | |||||
| May 17, 2016 at 10:32 | history | asked | galinette | CC BY-SA 3.0 |