Tomb/extras/kdf-keys
ATuinDev 35cf8572bf
Rename variable j to something more descriptive
Remove `+ 1` in conditions, easier to understand using the comparators
2018-02-03 23:24: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 Run extras/kdf-keys tests in travis 2018-02-03 21:23:07 +01:00
pbkdf2.c Rename variable j to something more descriptive 2018-02-03 23:24:20 +01:00
README imported python tomber into extras 2014-11-16 15:21:11 +01:00
test.sh Add check for password lens 2018-02-03 21:05:56 +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)