PHP 4.0 Bug #9383 Updated: mcrypt 2.4.9 function causes Apache to segfault
| From: | sniper@php.net | Date: | Mon, 05 Mar 2001 06:10:29 +0000 |
| Subject: | PHP 4.0 Bug #9383 Updated: mcrypt 2.4.9 function causes Apache to segfault | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-47955@lists.php.net to get a copy of this message | ||
ID: 9383
Updated by: sniper
Reported By: juraj@bednar.sk
Old-Status: Assigned
Status: Closed
Bug Type: mcrypt related
Assigned To:
Comments:
As this is clearly a bug in libmcrypt itself -> closed.
--Jani
Previous Comments:
---------------------------------------------------------------------------
[2001-02-26 18:10:00] juraj@bednar.sk
OK, I've done some research. This code fails to run (segfaults with the same symptoms as PHP):
#include<mcrypt.h>
main() {
mcrypt_module_open("tripledes","/usr/local/lib/libmcrypt/algorithms","ecb","/usr/local/lib/libmcrypt/modes");
}
Anyway, what's interesting -> I have the module tripledes installed correctly (even in that
directory). But even the bundled ciphertest program does not find any working algorithms under
freebsd 4.2
---------------------------------------------------------------------------
[2001-02-21 18:09:03] derick@php.net
After some research, it might be a portabilty issue, as this same configuration works flawlessly on
linux (RedHAt 6.2)
I'll contact the author of libmcrypt
---------------------------------------------------------------------------
[2001-02-21 16:51:33] juraj@bednar.sk
2.4.7 does not work too.
---------------------------------------------------------------------------
[2001-02-21 16:40:57] juraj@bednar.sk
Does not work with 2.4.8, trying 2.4.7
---------------------------------------------------------------------------
[2001-02-21 16:26:03] juraj@bednar.sk
no problem. I'm just compiling it with 2.4.8, should I try only 2.4.7. Is 2.4.8 known to have
some problem?
---------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view the rest of the comments,
please view the bug report online.
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=9383&edit=2