Timeline for What is most secure way for one party to encrypt 4 bytes in less than 40 bytes, which will be publicly available?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 19, 2020 at 19:21 | comment | added | SEJPM | @pinhead AES in the middle here ensures that you don't have to remember all the fresh keys. If I understand correctly however, you can derive a key per-message securely. In that case you might as well use that for direct OTP-like encryption because AES in this case is just a method to derive a fresh random-looking key for each message. If you already do that, you can indeed skip AES (assuming the derived key looks cryptographically random). | |
| Nov 19, 2020 at 16:23 | comment | added | pinhead | If I understand correctly, we use a counter and a key as inputs to AES to generate a value that we then XOR with the message. Do we need the AES function at all then? If the key is secure and single-use can I not use it as a OTP as suggested by the other answer? | |
| Nov 19, 2020 at 16:00 | history | answered | SEJPM | CC BY-SA 4.0 |