Llewellyn/Tomb
1
0
Fork 0
mirror of https://github.com/Llewellynvdm/Tomb.git synced 2024-12-23 02:28:58 +00:00
Code Issues Packages Projects Releases Wiki Activity
d135730386
Tomb/extras/kdf-keys
History
Jaromil 187a627022 Fix tomb-kdb-pbkdf2 helper for multiplatform build 
Avoid EOF being missed when reading in the password. Replace undefined
char-to-int comparison with a int-to-int one. Fix #360
2019-08-22 11:47:58 +02: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 Fix tomb-kdb-pbkdf2 helper for multiplatform build 2019-08-22 11:47:58 +02:00
README imported python tomber into extras 2014-11-16 15:21:11 +01:00
test.sh Don't impose any limitation in password size 2018-02-04 20:53:35 +01:00
test.txt fixed versioning and extras reorganization 2013-09-08 16:10:19 +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-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)