Timeline for Using one-way hash functions as the encryption method
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 3, 2013 at 19:42 | comment | added | jj57 | Yes that was the intention originally, not reusing words. However perhaps a unique IV could be sent with each message. Then that is used in creating the hash for each word. This would involve recomputing the database for each message though. Depending on computer/server speed/capability this may be OK. With a multi CPU/multi core server this would be done in a under a minute. Ilmari Karonen [posted a modification]( crypto.stackexchange.com/a/10156/8220) which could work too. | |
| Sep 3, 2013 at 15:01 | comment | added | e-sushi | While I understand what you're pointing at, I can't help posting this tongue-in-cheek comment saying that it would be dangerous to use such languages too. While some crypto-freaks out there actually speak "Tolkien's Elvish", others have (at least) thrown some analytics towards such languages. I know I did about 3 years ago, finding out that Elvish has letter-frequency problems just like every other language. Same applies to Star Trek's Klingon too btw. ;) | |
| Sep 3, 2013 at 12:17 | history | answered | LateralFractal | CC BY-SA 3.0 |