From c8282158193b3d403bf1dfec965a96e7516fe26e Mon Sep 17 00:00:00 2001
From: davidsarah <>
Date: Sun, 11 Oct 2009 02:14:36 +0000
Subject: [PATCH] K1 and plaintext might be encrypted by different enc. schemes

[Imported from Trac: page NewCaps/WhatCouldGoWrong, version 14]
---
 NewCaps/WhatCouldGoWrong.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/NewCaps/WhatCouldGoWrong.md b/NewCaps/WhatCouldGoWrong.md
index 1137d70..0448f37 100644
--- a/NewCaps/WhatCouldGoWrong.md
+++ b/NewCaps/WhatCouldGoWrong.md
@@ -4,10 +4,10 @@ This is about What Could Go Wrong with the "Elk Point 2" immutable file caps: <h
 |---|---|---|---|---|---|---|
 |#|*what bad thing could happen*|*how*|*who could do it*|*what could they target*|*what crypto property prevents it*|*how expensive to brute force* [5]footnote|
 |1|shape-shifter immutable file [1]footnote|collide read-cap (*R*,*T*)|creator of a file|their own file|the hash function's and cap format's collision resistance on the read-cap (*R*,*T*). This also depends on the encryption of *K1* being deterministic and correct.|2^(*n*+*t*)/2^|
-|2|unauthorized read|attack the encryption of *K1* with *R*|anyone|any one file|the cipher's security and the secrecy of the read-key *R*|2^*n*^|
+|2|unauthorized read|attack the encryption of *K1* with *R*|anyone|any one file|the security of the encryption scheme used for *K1*, and the secrecy of the read-key *R*|2^*n*^|
 |3|forgery of immutable file|generate a matching read-cap (*R*,*T*) for someone else's file|anyone|any one file|the hash function's and cap format's second-pre-image resistance on (*R*,*T*). This also depends on the encryption of *K1* being deterministic and correct.|2^*n*+*t*^|
 |4|roadblock or speedbump [2]footnote|generate (*K1enc*,*Dhash*,*V*) that hash to someone else's *T*, and copy their *S*|anyone|any one file|the hash function's and cap format's collision resistance on *T*|2^*t*^|
-|5|unauthorized read|attack the encryption of the plaintext with *K1*|anyone|any one file|the cipher's security and the secrecy of the encryption key *K1*|2^*k*^|
+|5|unauthorized read|attack the encryption of the plaintext with *K1*|anyone|any one file|the security of the encryption scheme used for the plaintext, and the secrecy of the encryption key *K1*|2^*k*^|
 |6|unauthorized read|figure out the input to the hash function that generates *S*|anyone|any one file|the hash function's pre-image resistance on *S*|brute force on *R* is !#2|
 |7|unauthorized deletion|brute force KD|anyone|any one file|secrecy of *KD*|2^*d*^|
 |8|unauthorized deletion|figure out the destroy key KD from Dhash|anyone|any one file|the hash function's pre-image resistance on *Dhash*|2^min(*d*,*dh*)^|