1e9e98aa0d
as proposed in RFC 3447 only one error return code is used when there are errors while decoding the pkcs#1 format. also, all steps are executed and only the "output" is skipped if something went wrong. Sorry this could break backwards compatibility, since there's no more BUFFER_OVERFLOW messaging. Former error-handling code could also be affected because now there's only OK as return code in cases where "res" is also set to '1'. |
||
---|---|---|
demos | ||
doc | ||
notes | ||
src | ||
testprof | ||
.gitignore | ||
.travis.yml | ||
build.sh | ||
changes | ||
coverage.sh | ||
coverity.sh | ||
crypt.tex | ||
Doxyfile | ||
filter.pl | ||
fixupind.pl | ||
genlist.sh | ||
libtomcrypt_VS2005.sln | ||
libtomcrypt_VS2005.vcproj | ||
libtomcrypt_VS2008.sln | ||
libtomcrypt_VS2008.vcproj | ||
libtomcrypt.dsp | ||
libtomcrypt.pc.in | ||
LICENSE | ||
makefile | ||
makefile.icc | ||
makefile.mingw | ||
makefile.msvc | ||
makefile.shared | ||
makefile.unix | ||
mess.sh | ||
parsenames.pl | ||
printinfo.sh | ||
README.md | ||
run.sh | ||
testbuild.sh | ||
testme.sh | ||
TODO | ||
updatemakes.sh |
libtomcrypt
See doc/crypt.pdf for a detailed documentation
Project Status
Submitting patches
Please branch off from develop if you want to submit a patch.
Branches
Please be aware, that all branches besides master and develop can and will be force-pushed, rebased and/or removed!
If you want to rely on such an unstable branch, create your own fork of this repository to make sure nothing breaks for you.