Timeline for Are there secure stream ciphers that cannot be parallelized?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 17, 2012 at 19:46 | comment | added | Cray | Thank's for this answer, very informative, it even goes in depth into different ways the question could be interpreted. | |
| Oct 17, 2012 at 19:38 | vote | accept | Cray | ||
| Oct 16, 2012 at 18:52 | comment | added | Ilmari Karonen | @Paŭlo: Depends on exactly what the "desired property" is, which I'm not too clear about. By my reading of the question, something like iterated (or arbitrarily extended) scrypt would seem closer to what he wants (paraphrased, "if I run this for a year on a fast CPU and then extract a value, nobody else should be able to derive the same value without spending at least a year on it unless they have a faster CPU"). | |
| Oct 16, 2012 at 17:29 | comment | added | Paŭlo Ebermann | One could simply derive the actual stream cipher key using scrypt from some initial non-secret, which would give about the desired property. | |
| Oct 16, 2012 at 15:21 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
added 2210 characters in body
|
| Oct 16, 2012 at 14:48 | history | answered | Ilmari Karonen | CC BY-SA 3.0 |