|File Search||Catalog||Content Search|
libmcrypt supports the algorithms: BLOWFISH, TWOFISH, DES, TripleDES, 3-WAY, SAFER-sk64, SAFER-sk128, SAFER+, LOKI97, GOST, RC2, RC6, MARS, IDEA, RIJNDAEL-128, RIJNDAEL-192, SERPENT, RIJNDAEL-256, CAST-128 (known as CAST5), CAST-256, ARCFOUR, ENIGMA, PANAMA, XTEA and WAKE. Block algorithms can be used in: CBC, ECB, CFB and OFB (8 bit and n bit, where n is the size of the algorithm's block length).
More information can be found at the libmcrypt homepage http://mcrypt.sourceforge.net/ .
Libmcrypt is a thread-safe library providing a uniform interface to access several block and stream encryption algorithms. Check the manual page for more information on libmcrypt. Look at COPYING for license information and the individual files for more information. COPYING applies only for the mcrypt program and not the algorithms which most of them are public domain. A mailing list on mcrypt more»
Mcrypt 2.1 was insecure (vulnerable to brute force attack for weak keys) because it just used the plainkey as it was given by the user as algorithm's key. The solution seems to be a function which tranforms the key given by the user to a real -random looking- key. There are many functions that may convert a password or a passphrase to a key. Most of them use hash algorithms. You can find some i more»
The xTEA algorithm may not be right implemented. There are two different behaved implementations, because the specification is not clear. I assumed that the C code in the specification is right, so in mcrypt xtea behaves exactly as the code shown in the specification. The different approach is the code in ftp.funet.fi which seems to be more rational than the code in the specification. But since more»
libmcrypt (2.5.7-5) unstable; urgency=low * updated the description about the new algorithms * more»
2003-03-08 17:30 nmav * NEWS, configure.in, lib/Makefile.am: mcrypt_symb.c is only generated wh more»
- Documentation- documentation-... - Find test vectors for PANAMA and WAKE and check the implementat more»
Author: Nikos Mavroyanopoulos <email@example.com>. The author says in the README file: Look at COPYING more»