command line arg checks
minor updates
clean up some warnings
update debug
merge from ecky-l version 2.1
Added tag 2.1 for changeset 7e1ab2539ef9
merge from ecky-l version 2.1
make more robust
bump to 2.1.1
copyrights; bump to 2.1.1
update distclean
update hgignore
update for 2.1.1
Added tag 2.1.1 for changeset fd995bf044f5
some options for data and key input, CMakeLists.txt
some options for data and key input, CMakeLists.txt
added some options for data/key input and output formatting
added some options for data/key input and output formatting
update readme
32 bit builds
warning fixes
update readme; 2.0
remove debug
Added tag 2.0 for changeset 2d1b828eb14b
makefile fixes for win
add hmac; version 2.0
Added tag 2.0 for changeset 33ffd5991204
Problem with null character
I decided that it would be better left as is. There are other issues with text strings in Tcl besides just null bytes and I feel it will be safer to just warn the user about using binary data within text strings.
update .hgignore
version 1.0: update usage
tests
dosify readme
This has to do with the way Tcl handles null bytes. It does not pass the actual nulls to the sha procedure. You will have to get that data into a file and use the -file option. % load sha.so % sha 512 \0 buf:��: len: 2 (obviously incorrect) % set fh [open t3 r] file3 % fconfigure $fh -translation binary % gets $fh line 1 % sha 512 $line buf:��: len: 2 6fd901d780c0e8c28b48600e2d94009789a8eacbd9186fcbea73e8a60c7eaf684175ffe7e4c3c1b5f8f92b14a923d56c0e4102edf92408a8eb9ee24adf4efacf % string length $line...
Problem with null character
add support for 512/256 and 512/224
add validation msg
add readme
initial checkin