Timeline for AES blocks with a counter
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 13, 2018 at 20:55 | history | edited | kelalaka | CC BY-SA 4.0 | update after question update. |
| Oct 13, 2018 at 17:42 | comment | added | kelalaka | @isak I agree with Maarten's last comment. | |
| Oct 13, 2018 at 17:38 | comment | added | isak | Thank you for your detailed answers. I added some more info to the question. Is it enough information? Using GCM will add more bytes to the packet. If possible I would like to keep the packet as small as possible. | |
| Oct 13, 2018 at 11:06 | history | edited | kelalaka | CC BY-SA 4.0 | explain more |
| Oct 13, 2018 at 10:43 | comment | added | kelalaka | He tries to make the messages unique by adding an internal counter. In this case ECB is secure right? Yes GCM by standard has random IV's and I don't say change that. I did not to say use GCM and AES-CTR without IV. Let me re-check. Thanks. | |
| Oct 12, 2018 at 23:49 | comment | added | Maarten Bodewes♦ | "If you are talking about the CBC or CTR mode, yes you can use ECB". I don't get this sentence. "No need to add a counter to make them unique." Uh, I'd make very sure that the IV is unique for GCM - your answer doesn't highlight this. Just a counter in the message instead of an IV is very dangerous for GCM, even more so than just for AES-CTR. | |
| Oct 12, 2018 at 21:51 | history | answered | kelalaka | CC BY-SA 4.0 |