aboutsummaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2014-08-17 19:40:42 +0200
committerMattias Andrée <maandree@operamail.com>2014-08-17 19:40:42 +0200
commit78c382437e6e18e2867f2ddab9bebfe6223f24cc (patch)
treec1d01f813f344c7a45acf01df01ac446e392882f /README
parentadd copying and license (diff)
downloadfile2key-78c382437e6e18e2867f2ddab9bebfe6223f24cc.tar.gz
file2key-78c382437e6e18e2867f2ddab9bebfe6223f24cc.tar.bz2
file2key-78c382437e6e18e2867f2ddab9bebfe6223f24cc.tar.xz
typo + add readme
Signed-off-by: Mattias Andrée <maandree@operamail.com>
Diffstat (limited to 'README')
-rw-r--r--README11
1 files changed, 11 insertions, 0 deletions
diff --git a/README b/README
new file mode 100644
index 0000000..0cb5b27
--- /dev/null
+++ b/README
@@ -0,0 +1,11 @@
+A simple command that generates a key from a file and a passphrase.
+
+file2key uses Keccak[] to create a hash as big as a selected file
+and the prints the bitwise exclusive or of the hash and the file
+making a keyfile from any normal file and a passphrase. The idea
+is the reversed of steganography.
+
+file2key cannot be configured. The idea behind this is that you
+if it required configurations you run the risk of losing all your
+keys if you lose your configurations. This must not happen.
+