13 Commits

Include renames

Author	SHA1	Message	Date
Steffen Jaeckel	4a8bfc0a21	introduce CRYPT_INPUT_TOO_LONG	2017-09-27 21:34:11 +02:00
Steffen Jaeckel	33e70b427a	CRYPT_INVALID_KEYSIZE isn't only used for block ciphers	2017-08-26 12:03:35 +02:00
Steffen Jaeckel	fe19dad623	replace SVN tags	2017-06-20 15:16:11 +02:00
Steffen Jaeckel	4dc211e19d	clean-up headers	2017-06-20 15:16:11 +02:00
Steffen Jaeckel	08503a02f5	update error codes ... This closes #180	2017-03-31 15:12:12 +02:00
Francois Perrad	58353f51e2	remove trailing spaces	2017-02-24 16:29:54 +01:00
Francois Perrad	cebf33cdce	add some const	2017-02-24 16:23:23 +01:00
Jonathan Herzog	ff736a61bb	Hash functions now check for input-length overflow. ... Because many of the hash-functions implemented by LTC use the length of the input when padding the input out to a block-length, LTC keeps track of the input length in a 64-bit integer. However, it did not previously test for overflow of this value. Since many of the hash-functions implemented by LTC are defined for inputs of length 2^128 bits or more, this means that LTC was incorrectly implementing these hash functions for extremely long inputs. Also, this might have been a minor security problem: A clever attacker might have been able to take a message with a known hash and find another message (longer by 2^64 bits) that would be hashed to the same value by LTC. Fortunately, LTC uses a pre-processor macro to make the actual code for hashing, and so this problem could be fixed by adding an overflow-check to that macro.	2014-08-06 19:06:00 +02:00
Tom St Denis	bbc52b9e1b	added libtomcrypt-1.17	2010-06-16 12:39:13 +02:00
Tom St Denis	64d7ebe166	added libtomcrypt-1.11	2010-06-16 12:38:54 +02:00
Tom St Denis	3964a6523a	added libtomcrypt-1.03	2010-06-16 12:38:34 +02:00
Tom St Denis	6ac9952498	added libtomcrypt-1.01	2010-06-16 12:38:29 +02:00
Tom St Denis	bfc2f5b078	added libtomcrypt-1.00	2010-06-16 12:38:26 +02:00