Timeline for Cipher recommendation for known-plaintext attack
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 19, 2019 at 11:59 | vote | accept | Miguel | ||
| Aug 19, 2019 at 8:12 | comment | added | Miguel | @Ilmari No, neither the plain-text nor the cipher-text can be influenced by the user. | |
| Aug 19, 2019 at 8:10 | comment | added | Miguel | @Patriot No more than 10 | |
| Aug 16, 2019 at 12:08 | comment | added | Ilmari Karonen | Do you need resistance to forgery or other active (i.e. chosen-plaintext / chosen-ciphertext) attacks? And if so, what's an acceptable probability for a fake/modified ciphertext being accepted? (You can't really make it less than one in $10^7$ with your constraints, but that limit can be achieved.) | |
| Aug 16, 2019 at 10:50 | comment | added | Patriot | @Miguel How many plaintexts / ciphertexts will there be? | |
| Aug 16, 2019 at 8:46 | answer | added | Andy | timeline score: 1 | |
| Aug 16, 2019 at 6:13 | comment | added | Miguel | @SEJPM Thanks, I'll check it out | |
| Aug 16, 2019 at 6:13 | comment | added | Miguel | @Andy Symmetric cipher | |
| Aug 15, 2019 at 18:26 | comment | added | SEJPM | Format-Preserving Encryption (FPE) can probably do this. | |
| Aug 15, 2019 at 15:30 | comment | added | Andy | Do you need a symmetric or asymmetric cipher? | |
| Aug 15, 2019 at 14:55 | review | First posts | |||
| Aug 15, 2019 at 18:36 | |||||
| Aug 15, 2019 at 14:51 | history | asked | Miguel | CC BY-SA 4.0 |