Tomb/extras/kdf-keys
ATuinDev 257e5ee99a
whitespaces are now part of the password
NULL character can also be part of the password. There was a failing
test that was checking exactly that (now all the tests pass).
2018-02-03 19:16:20 +01:00
..
.gitignore fixed versioning and extras reorganization 2013-09-08 16:10:19 +02:00
benchmark.c fixed versioning and extras reorganization 2013-09-08 16:10:19 +02:00
gen_salt.c fixed versioning and extras reorganization 2013-09-08 16:10:19 +02:00
hexencode.c fixed versioning and extras reorganization 2013-09-08 16:10:19 +02:00
Makefile documentation and makefile scripts updates for release 2014-11-26 20:28:28 +01:00
pbkdf2.c whitespaces are now part of the password 2018-02-03 19:16:20 +01:00
README imported python tomber into extras 2014-11-16 15:21:11 +01:00
test.sh Add test testing that whitespaces are used by kdf wrapper 2018-02-03 19:12:05 +01:00
test.txt fixed versioning and extras reorganization 2013-09-08 16:10:19 +02:00

BUILD
------

Just type make.
You need a recent development version of libgcrypt installed.
On Debian 7 (not earlier) the libgcrypt11-dev package works:
 # apt-get install libgcrypt11-dev

PLANS
------

While this can be useful for general purpose, it specially fits tomb, and it's designed for easy integration and compilation.

Binary name will then be:
tomb-kdb-${algo}
tomb-kdb-${algo}-gensalt
tomb-kdb-${algo}-getiter
tomb-kdb-hexencode

Base64 vs hexencode
-------------------

While base64 is easier to use (shell command, more compact), pbkdf2 use hex
in its specifications.
This could be solved with an option (-x for hex, defaults to base64)