Edit report at http://bugs.php.net/bug.php?id=53496&edit=1

 ID:                 53496
 Updated by:         der...@php.net
 Reported by:        ulrich1992 at web dot de
 Summary:            strange bug with mcrypt, base64 and mysql
 Status:             Feedback
 Type:               Bug
 Package:            mcrypt related
 Operating System:   Windows XP SP3 Professional
 PHP Version:        5.3.1RC2
 Block user comment: N
 Private report:     N

 New Comment:

Also, you need to provide a *short* reproducible script. Not your whole
webshop.


Previous Comments:
------------------------------------------------------------------------
[2010-12-08 13:21:39] paj...@php.net

Please try with a decent version, like 5.3.4RC2 or 5.3.3.

------------------------------------------------------------------------
[2010-12-08 12:44:29] ulrich1992 at web dot de

Description:
------------
I'm doing a webshop system, and I think, I have found a strange bug in
mcrypt.

I have to encrypt a string with a number(secret PIN), then encode it
with base64, and insert it to a datebase (MySQL).



Then in the admin frontend for my shop, I have to decode and decrypt it,
to show it to the shop administrator.

This works in the most of cases. But for example when the PIN is "1234"
and the key is "ganzgehein", and I try to decrypt it, it only produces
binary rubbish, instead of the expected PIN.

I can't reproduce this bug in a single example file, so i have to upload
my complete project. Sorry it's in german language, but there is not
very much text, so I think you can understand it by using a automatic
translator like Googles.



PS: I am using XAMPP

Test script:
---------------
http://www.file-upload.net/download-3032467/mcrypt_bug_demo.zip.html



It's hosted on file-upload.net because I can't install a ftp client on
this machine.

Expected result:
----------------
See notice_for_bugreport.txt for details.



------------------------------------------------------------------------



-- 
Edit this bug report at http://bugs.php.net/bug.php?id=53496&edit=1

Reply via email to