Timeline
2009-10-15:
- 17:14 NewCapDesign edited by
- (diff)
- 17:13 NewCapDesign edited by
- zooko asked me to put this here for later review (diff)
- 16:51 Ticket #814 (v1.4.1 storage servers sending a negative number for ...) created by
- I'm looking at the logs of allmydata.com user gar5 and I see this. I …
- 16:37 Ticket #813 (string exception raised to web renderer?) created by
- In the twistd.log of allmydata.com user gar5 I find this exception: […]
- 05:04 NewCaps/WhatCouldGoWrong edited by
- add URL for post about multicollision attacks (diff)
- 04:40 NewCaps/WhatCouldGoWrong edited by
- multicollision attacks (diff)
2009-10-13:
- 15:34 PatchReviewProcess created by
- how to review patches
- 15:27 Dev edited by
- link to PatchReviewProcess (diff)
2009-10-12:
- 22:33 WikiStart edited by
- presentation at HadoopWorld? (diff)
2009-10-11:
- 21:13 WikiStart edited by
- Karmic inclusion news (diff)
- 20:06 NewCaps/WhatCouldGoWrong edited by
- set URLs back to fixed versions on jacaranda.org (diff)
- 17:29 NewCaps/WhatCouldGoWrong edited by
- cleanup (diff)
- 17:28 NewCaps/WhatCouldGoWrong edited by
- parenthesize p/N to avoid possible misreading (diff)
- 16:57 NewCaps/WhatCouldGoWrong edited by
- correct formula for cost of collision attack #1 (diff)
- 16:17 NewCaps/WhatCouldGoWrong edited by
- cost of attack #12 is not relevant because attack #3 is strictly better (diff)
- 16:14 NewCaps/WhatCouldGoWrong edited by
- #7 and #8 are really the same attack; merge and renumber (diff)
- 16:09 NewCaps/WhatCouldGoWrong edited by
- resistance to attack #7 depends on onewayness of hash (diff)
- 16:05 NewCaps/WhatCouldGoWrong edited by
- footnote 5 no longer applicable; remove and renumber (diff)
- 16:00 NewCaps/WhatCouldGoWrong edited by
- fix formatting of superscripts; expand n/a (diff)
- 15:52 NewCaps/WhatCouldGoWrong edited by
- generalize attack costs for low-success-probability and multi-target … (diff)
- 15:30 NewCaps/WhatCouldGoWrong edited by
- SHA-256d does not help for attacks in footnote 7 (diff)
- 15:21 NewCaps/WhatCouldGoWrong edited by
- footnote 7 applies to SHA-256 (diff)
- 15:18 NewCaps/WhatCouldGoWrong edited by
- (diff)
- 15:17 NewCaps/WhatCouldGoWrong edited by
- note attacks better than brute-force on Merkle-Damgård hashes (diff)
- 14:00 NewCaps/WhatCouldGoWrong edited by
- correction to effective hash length for accidental collisions (diff)
- 04:04 NewCaps/WhatCouldGoWrong edited by
- link to my version of the diagram where I changed n to r (diff)
- 03:47 NewCaps/WhatCouldGoWrong edited by
- go back to using r = bitlength(R) (diff)
- 03:41 NewCaps/WhatCouldGoWrong edited by
- KD in #8 need not be the original KD (diff)
- 03:39 NewCaps/WhatCouldGoWrong edited by
- move URL relevant to footnote 2 (diff)
- 03:34 NewCaps/WhatCouldGoWrong edited by
- add footnote 6 (diff)
- 03:29 NewCaps/WhatCouldGoWrong edited by
- s = bitlength(S) (diff)
- 03:24 NewCaps/WhatCouldGoWrong edited by
- typo (diff)
- 02:49 NewCaps/WhatCouldGoWrong edited by
- clarification to #6 (diff)
- 02:48 NewCaps/WhatCouldGoWrong edited by
- (diff)
- 02:39 NewCaps/WhatCouldGoWrong edited by
- attack #6 depends on onewayness, not preimage resistance (diff)
- 02:29 NewCaps/WhatCouldGoWrong edited by
- pre-image -> preimage (diff)
- 02:27 NewCaps/WhatCouldGoWrong edited by
- attack #4 depends on second-preimage resistance, not collision resistance (diff)
- 02:24 NewCaps/WhatCouldGoWrong edited by
- cost of attack #2 (diff)
- 02:20 NewCaps/WhatCouldGoWrong edited by
- hash length for accidental collisions (diff)
- 02:17 NewCaps/WhatCouldGoWrong edited by
- security and seeding of RNG that generated K1 (diff)
- 02:14 NewCaps/WhatCouldGoWrong edited by
- K1 and plaintext might be encrypted by different enc. schemes (diff)
- 02:07 NewCaps/WhatCouldGoWrong edited by
- cost of #8 (diff)
- 01:54 NewCaps/WhatCouldGoWrong edited by
- accidental collision; footnote 5 (diff)
- 01:42 NewCaps/WhatCouldGoWrong edited by
- can deny service by attacking the network (diff)
- 01:36 NewCaps/WhatCouldGoWrong edited by
- (diff)
- 01:35 NewCaps/WhatCouldGoWrong edited by
- formatting (diff)
- 01:34 NewCaps/WhatCouldGoWrong edited by
- fix undeletion attacks (diff)
- 01:18 NewCaps/WhatCouldGoWrong edited by
- add attack on verify cap (diff)
- 01:01 NewCaps/WhatCouldGoWrong edited by
- add denial-of-service (diff)
- 00:50 NewCaps/WhatCouldGoWrong edited by
- r -> n (r would have been more consistent, but n is what the diagram uses) (diff)
- 00:45 NewCaps/WhatCouldGoWrong edited by
- (diff)
- 00:43 NewCaps/WhatCouldGoWrong edited by
- fix typos and some variable names (diff)
2009-10-10:
- 21:58 NewCaps/WhatCouldGoWrong edited by
- whee more attacks (diff)
- 20:52 NewCaps/WhatCouldGoWrong created by
- What Could Go Wrong
Note: See TracTimeline
for information about the timeline view.