Timeline for Encrypting/Decrypting sensitive information for storage purpose
Current License: CC BY-SA 4.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 16, 2019 at 21:39 | history | edited | kelalaka | CC BY-SA 4.0 |
Corrected the AES-CMC for CryptDB's DET onion.
|
Apr 16, 2019 at 20:46 | history | edited | kelalaka | CC BY-SA 4.0 |
polish
|
Apr 16, 2019 at 17:12 | history | edited | kelalaka | CC BY-SA 4.0 |
update per comments, thanks to Ilmari and Squeamish
|
Apr 16, 2019 at 2:59 | comment | added | Squeamish Ossifrage | ‘ECB mode’ is a mistake of a concept that should be abolished, even moreso than the misbegotten ontology of ‘block cipher modes of operation’. Just call it AES if you want to use it on a single block; just go straight to shooting yourself in the foot if you have multiple blocks. | |
Apr 15, 2019 at 15:01 | comment | added | Ilmari Karonen | Do not use ECB mode, at least not unless you're sure that all your values will fit in a single AES block (16 bytes). If you want a general-purpose encryption scheme that allows equality comparison on encrypted data, use AES-SIV. | |
Apr 15, 2019 at 14:38 | history | edited | kelalaka | CC BY-SA 4.0 |
m1 was a typo. Thanks to Paul
|
Apr 15, 2019 at 14:37 | comment | added | kelalaka | @PaulUszak Ah, thanks that is typo.. | |
Apr 15, 2019 at 14:32 | comment | added | Paul Uszak | Do all the ones and twos make sense in that equality equation? | |
Oct 17, 2018 at 13:38 | history | edited | kelalaka | CC BY-SA 4.0 |
explain more
|
Oct 17, 2018 at 13:22 | history | edited | kelalaka | CC BY-SA 4.0 |
updated the answer.
|
Sep 26, 2018 at 20:59 | history | answered | kelalaka | CC BY-SA 4.0 |