mirror of
https://github.com/Llewellynvdm/Tomb.git
synced 2024-11-13 16:26:28 +00:00
257e5ee99a
NULL character can also be part of the password. There was a failing test that was checking exactly that (now all the tests pass). |
||
---|---|---|
.. | ||
.gitignore | ||
benchmark.c | ||
gen_salt.c | ||
hexencode.c | ||
Makefile | ||
pbkdf2.c | ||
README | ||
test.sh | ||
test.txt |
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)