From 109979bc4515121fa8b583ab41e8476d1a9790ee Mon Sep 17 00:00:00 2001 From: zooko <> Date: Sat, 10 Oct 2009 20:52:21 +0000 Subject: [PATCH] What Could Go Wrong [Imported from Trac: page NewCaps/WhatCouldGoWrong, version 1] --- NewCaps/WhatCouldGoWrong.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 NewCaps/WhatCouldGoWrong.md diff --git a/NewCaps/WhatCouldGoWrong.md b/NewCaps/WhatCouldGoWrong.md new file mode 100644 index 0000000..552aa4c --- /dev/null +++ b/NewCaps/WhatCouldGoWrong.md @@ -0,0 +1,10 @@ +This is about What Could Go Wrong with the "Elk Point 2" immutable file caps: + +| | | | | | +|---|---|---|---|---| +|*what bad thing could happen*|*who could do it*|*what could they target*|*what crypto property prevents it*|*how expensive to brute force*| +|shape-shifter immutable file [1]footnote|creator of a file|their own file|the hash function's and cap format's collision resistance on the read-cap (*R*,*T*)|2^(*r*+*t*)/2^| +|unauthorized read|anyone|any file|the cipher's security and the secrecy of the read-key *R*|2^*r*^| +|forgery of immutable file|anyone|any file|the hash function's and cap format's second-pre-image resistance on (*R*,*T*)|2^*r*+*t*^| + +1. *shape-shifter immutable file*: creator creates more than one file matching the immutable file readcap