Llewellyn/Tomb
1
0
Fork 0
mirror of https://github.com/Llewellynvdm/Tomb.git synced 2024-11-13 08:16:29 +00:00
Code Issues Packages Projects Releases Wiki Activity
bc3177141d
Tomb/extras/kdf
History
Jaromil 710eb5c458 make install for extras/kdf
2013-06-11 17:34:01 +00:00
..
.gitignore Directory reorganization 2013-05-18 17:29:37 +02:00
benchmark.c fix to build KDF key protection algorithms 2013-06-11 17:21:06 +00:00
gen_salt.c fix to build KDF key protection algorithms 2013-06-11 17:21:06 +00:00
hexencode.c Directory reorganization 2013-05-18 17:29:37 +02:00
Makefile make install for extras/kdf 2013-06-11 17:34:01 +00:00
pbkdf2.c fix to build KDF key protection algorithms 2013-06-11 17:21:06 +00:00
README fix to build KDF key protection algorithms 2013-06-11 17:21:06 +00:00
test.sh Directory reorganization 2013-05-18 17:29:37 +02:00
test.txt Directory reorganization 2013-05-18 17:29:37 +02:00

README 

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-kdf-${algo}
tomb-kdf-${algo}-gensalt
tomb-kdf-${algo}-getiter

hexencode (or similar utils, should they be developed), go with:
tomb-utils-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)