Timeline for Implications of hashing to UTF-8 in a cryptographic function
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 7, 2015 at 1:03 | comment | added | ThoriumBR | UTF-64 is the binary representation on an IP address when IPv12 starts rolling out. </joke> | |
| S Sep 5, 2015 at 19:03 | history | suggested | Navin | CC BY-SA 3.0 |
No such thing as UTF-64
|
| Sep 5, 2015 at 18:07 | review | Suggested edits | |||
| S Sep 5, 2015 at 19:03 | |||||
| Sep 5, 2015 at 14:21 | comment | added | Maarten Bodewes | What's "UTF-64"? | |
| Sep 5, 2015 at 14:20 | comment | added | Maarten Bodewes | "I am not aware of any implementation that uses a different one." I am, so does Wikipedia | |
| Sep 4, 2015 at 1:49 | comment | added | Criticizing Israel not allowed | In general the hash function will not return any encoding. Some will encode as hexadecimal. | |
| Sep 4, 2015 at 1:28 | comment | added | Ilmari Karonen |
Re: variant Base64 alphabets, there's always base64url, which uses - and _ instead of + and /.
|
|
| Sep 3, 2015 at 23:10 | comment | added | Paul Draper |
FYI, as far a character variants go, bouncy castle pads with . instead of =. "URL-safe" base64 uses - and _ instead of + and /, though those are less common. And whitespace is frequently added.
|
|
| Sep 3, 2015 at 21:24 | comment | added | Asa | I was pretty confused about how it all works, and you cleared up a lot of things for me. Particularly the wiki comment. And what Base64 encoding actually is, I thought it was more or less ASCII. Thanks! | |
| Sep 3, 2015 at 21:00 | vote | accept | Asa | ||
| Sep 3, 2015 at 20:53 | history | answered | ThoriumBR | CC BY-SA 3.0 |