From 25fdb9869ef45b6e3fe5d5d9f6ff57cc2017b713 Mon Sep 17 00:00:00 2001
From: Jeff Connelly <shellreef+git@gmail.com>
Date: Thu, 15 May 2008 18:48:03 -0700
Subject: [PATCH] Add TODO list.

---
 TODO | 32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 TODO

diff --git a/TODO b/TODO
new file mode 100644
index 0000000..bdd593e
--- /dev/null
+++ b/TODO
@@ -0,0 +1,32 @@
+Things To Do    
+Jeff Connelly
+
+To do:
+- Channel filling
+Send blank message (padded, of course, to a high multiple), every day.
+Send no more than one message per day, and queue to send always at the same time.
+Mitigate timing attacks.
+
+- Destructive one-time pads
+Rewrite parts of the pad. With what? Does it matter if it is detected that
+they were overwritten? If not, can just write with zeros. Better strategy
+probably to take truly random data from another source, and rewrite the part
+of the file, saving it to a new temporary file. Securely delete old one.
+Does it matter if pads mismatch on both sides, giving an attacker an advantage?
+See also: rewriting pads.
+
+- Encrypting pads
+Try Libtomcrypt, symmetric encryption with passphrase through secure key hash
+function.
+
+- Tools to break two-time pads
+Fun. Do this.
+
+- Rewriting pads to falsify previously-sent messages 
+(related to repuditation)
+Similar to destructive one-time pads, but manual rewriting, and with a 
+message, instead of automatic.
+
+COMPLETED:
+- Padding
+- Basic pad loading and encryption/decryption of both message formats
-- 
2.11.4.GIT