From 7697b98dd5a485116960b0458f909fdac9e54524 Mon Sep 17 00:00:00 2001
From: davidsarah <>
Date: Sun, 11 Oct 2009 01:35:12 +0000
Subject: [PATCH] formatting

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

diff --git a/NewCaps/WhatCouldGoWrong.md b/NewCaps/WhatCouldGoWrong.md
index c476ee8..1f17250 100644
--- a/NewCaps/WhatCouldGoWrong.md
+++ b/NewCaps/WhatCouldGoWrong.md
@@ -19,7 +19,9 @@ This is about What Could Go Wrong with the "Elk Point 2" immutable file caps: <h
 where *k* = bitlength(*K1*), *n* = bitlength(*R*), *t* = bitlength(*T*), *u* = bitlength(*U*), *d* = bitlength(*KD*).
 
 1. *shape-shifter immutable file*: creator creates more than one file matching the immutable file readcap
+
 2. *roadblock*: attacker prevents uploader (including repairer) from being able to write a real share into the right storage index; *speedbump*: attacker adds his bogus share into the list of shares stored under the storage index by the same method; downloader has to download, examine, and discard the bogus (*K1enc*,*Dhash*,*V*)'s until it finds the real one
+
 3. *undeletion*: attacker makes a deleted file (for which it need not have had a read cap) accessible at its previous storage index, and readable by previous read caps
 
 <http://allmydata.org/pipermail/tahoe-dev/2009-October/002959.html>
\ No newline at end of file