Re: bug? php4 with libmcrypt-2.2.7

On Tue, 15 Aug 2000, Remco Chang wrote: > i have been battling libmcrypt for the past 2 days and came with zilch so > far... i am about to raise the white flag and submit it to the bug list > unless someone here could convince me otherwise... > > there is very little support/documentation on how php talks to libmcrypt. > after going through the source code, i noticed that the functions listed > on the web page http://www.php.net/manual/ref.mcrypt.php are > not all > implemented... the following are the only functions supported: > PHP_FE(mcrypt_ecb, NULL) > PHP_FE(mcrypt_cbc, NULL) > PHP_FE(mcrypt_cfb, NULL) > PHP_FE(mcrypt_ofb, NULL) > PHP_FE(mcrypt_get_cipher_name, NULL) > PHP_FE(mcrypt_get_block_size, NULL) > PHP_FE(mcrypt_get_key_size, NULL) > PHP_FE(mcrypt_create_iv, NULL) > > even then, mcrypt_ecb, cbc, cfb, ofb are not working correctly. instead > of returning srings, they return binary garbage. this is a huge problem > because the decrypt function takes a string as input. because of this, i > cannot go through the encrypt/decrypt process and get back the original > message that i wanted encrypted. Your analysis is completely wrong. Strings in PHP are 8-bit clean. The output of the encryption process almost always looks like "binary garbage" (if it would make sense to you, it would be a bad algorithm). PHP 4.0.2 supports libmcrypt 2.4.x and also adds some additional user-level functions. These are already documented in the manual (there should be a note about them being supported starting at 4.0.2. If not, please submit a documentation bug report). - Sascha