Bug #15503 Updated: Mcrypt segfaults if not correctly calling mcrypt_module_close()

From: Date: Mon, 11 Feb 2002 14:47:52 +0000
Subject: Bug #15503 Updated: Mcrypt segfaults if not correctly calling mcrypt_module_close()
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-126@lists.php.net to get a copy of this message
ID: 15503 Updated by: jukkaho@mail.student.oulu.fi Reported By: jukkaho@mail.student.oulu.fi Status: Closed Bug Type: mcrypt related Operating System: Linux PHP Version: 4.1.1 New Comment: Hmm.. previous one was with key "testing testing".. this is with key "test" as in example: 42<br> encrypted_text: í<9A>ùp¿Ý/^S<br> decrypted_text: ^@^@^@^@^@^@^@^@<br> So.. always 8 null characters. Previous Comments: ------------------------------------------------------------------------ [2002-02-11 09:44:50] jukkaho@mail.student.oulu.fi Ok, cvs version does not die with signals any more regardless what function calls I leave, but for some reason $decrypted_text seems to be empty (as in \0 characters) all the time. Something wrong in my code that should cause this? Source output from my code through less: 08<br> encrypted_text: 4U<83><9F>~5}<8C><br> decrypted_text: ^@^@^@^@^@^@^@^@<br> ------------------------------------------------------------------------ [2002-02-11 09:07:34] jukkaho@mail.student.oulu.fi I try and report back soon. ------------------------------------------------------------------------ [2002-02-11 08:49:47] derick@php.net Ah, it's already fixed in CVS. Can you try a snapshot from snaps.php.net ? Derick ------------------------------------------------------------------------ [2002-02-11 08:45:58] jukkaho@mail.student.oulu.fi Fatal error: Call to undefined function: mcrypt_generic_deinit() in ... PHP Version 4.1.1 confirms phpinfo(); How should I make a backtrace? There's no core. ------------------------------------------------------------------------ [2002-02-11 08:38:52] jukkaho@mail.student.oulu.fi Forgot to tell: apache 1.3.20 libmcrypt 2.4.22 ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/15503 -- Edit this bug report at http://bugs.php.net/?id=15503&edit=1

« previous php.bugs (#126) next »