Timeline for Is it insecure to use a hash with secret salt instead of a signature?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 10 at 12:22 | history | suggested | Toby Speight | CC BY-SA 4.0 | spelling fixes |
| Oct 10 at 8:26 | review | Suggested edits | |||
| S Oct 10 at 12:22 | |||||
| Oct 9 at 22:33 | history | edited | Maarten Bodewes♦ | CC BY-SA 4.0 | explained why asymmetric crypto is specifically slower for many small messsages |
| Oct 9 at 17:57 | vote | accept | Hounshell | ||
| Oct 9 at 17:57 | comment | added | Hounshell | Thank you, HMAC looks like the way to go. In this particular case replay attacks aren't a concern; we're just worried about whether the data originated from a trusted source, not whether the data is stale / duplicated. But good call-out anyway. | |
| Oct 9 at 17:16 | history | answered | Maarten Bodewes♦ | CC BY-SA 4.0 |