From 18ee108e6c0eb3701e7fef4137dcc24843564139 Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Sat, 9 Jan 2010 16:58:41 +0000
Subject: [PATCH] link to the twitter incident

[Imported from Trac: page TracSecurityOverview, version 2]
---
 TracSecurityOverview.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/TracSecurityOverview.md b/TracSecurityOverview.md
index 8aa1488..3482e44 100644
--- a/TracSecurityOverview.md
+++ b/TracSecurityOverview.md
@@ -5,7 +5,7 @@ This is just a quick'n'dirty document to help users make informed decisions abou
 
 ## Recommendations
 
-  * Don't use a password which you use elsewhere.  (See: Twitter incident)  [Find ref.]FIXME:
+  * Don't use a password which you use elsewhere.  (See: [Twitter incident](@@http://testgrid.allmydata.org:3567/file/URI:CHK:nm72blax6oqt3fui3dnrhahszq:wcpjaneyqzf4bw752izfey44abql6ywync2vweejsmnohyiwkkia:3:10:275196/@@named=/the-anatomy-of-the-twitter-attack.html@@)) (the short story is that there were no technical security flaws, but users used the same creds on an "unimportant" service as well as a different critical service, so the attacker could escalate the attack across services.)
   * Don't expect the ticket database to be non-corrupt or reliable or persistent.
     * Backup the ticket database and wiki pages regularly!  Use snapshots so corruption does not overwrite correct data. 
 
@@ -24,5 +24,4 @@ This is just a quick'n'dirty document to help users make informed decisions abou
 ## To Do
 
   * Search for existing Trac security references.
-  * Verify that plaintext passwords are stored.
-  * Find Twitter incident ref (the short story is that there were no technical security flaws, but users used the same creds on an "unimportant" service as well as a different critical service, so the attacker could escalate the attack across services.)
+  * Verify that plaintext passwords are stored.
\ No newline at end of file