Bug #10187 Updated: Warning: mcrypt module initialization failed

From: Date: Fri, 18 May 2001 09:03:28 +0000
Subject: Bug #10187 Updated: Warning: mcrypt module initialization failed
Groups: php.dev 
Request: Send a blank email to php-dev+get-55745@lists.php.net to get a copy of this message
ID: 10187 Updated by: jmoore Reported By: clewis@myfonts.com Status: Assigned Bug Type: mcrypt related Operating system: PHP Version: 4.0 Latest CVS (05/04/2001) Assigned To: derick Comments: Derick: Bug 10281 reports this on Linux. Probably not platform specific. Previous Comments: --------------------------------------------------------------------------- [2001-05-01 03:37:44] derick@php.net I guess this could be an OS specific problem. I've no access to a Mac OS X machine unfortunately. --------------------------------------------------------------------------- [2001-04-05 11:48:59] clewis@myfonts.com Incidentally, I tried the new-style mcrypt functions as Colin suggested, and got a similar warning: "Could not open encryption module." --------------------------------------------------------------------------- [2001-04-05 11:30:47] derick@php.net analysed > assigned --------------------------------------------------------------------------- [2001-04-05 11:30:06] derick@php.net Another mcrypt bug, I'll check this one out. It may be a platform depended bug BTW. --------------------------------------------------------------------------- [2001-04-05 11:29:52] cmv@php.net First, the "--disable-posix-threads" requirement for libmcrypt isn't a requirement anymore. As of libmcrypt 2.4.x, you don't need it. Second, I think you should be using the 2.4.x-style mcrypt functions. Look at example 2 at http://www.php.net/manual/en/ref.mcrypt.php Third, blowfish is broken in libmcrypt. It will encode/decode internally, but don't rely on it if you need to pass data to a non-PHP application (e.g. Perl). - Colin --------------------------------------------------------------------------- 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=10187&edit=2

« previous php.dev (#55745) next »