Timeline for Create a TOTP for machines using HMAC or AES
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 7:34 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Dec 19, 2020 at 21:00 | history | tweeted | twitter.com/StackCrypto/status/1340401540012630018 | ||
| Oct 25, 2020 at 23:09 | vote | accept | Brennino | ||
| Oct 22, 2020 at 2:28 | comment | added | user30713 | I'd consider both to be more than secure enough for your specification; much more than 5 years in fact. But to choose between them: I'd avoid encryption when a hash will do just on general principles. You have a 15-minute window so as long as the m is rounded down to the nearest 15-minute mark, and both sides have decent clocks, you don't need the ability for the receiver to decrypt the incoming message. | |
| Oct 18, 2020 at 15:54 | answer | added | fgrieu♦ | timeline score: 2 | |
| Oct 18, 2020 at 15:33 | history | edited | fgrieu♦ | CC BY-SA 4.0 |
Polish
|
| Oct 18, 2020 at 3:26 | review | First posts | |||
| Oct 18, 2020 at 13:33 | |||||
| Oct 18, 2020 at 3:26 | history | asked | Brennino | CC BY-SA 4.0 |