| Robert Edmonds 2007-08-31, 7:13 am |
| Graham Dumpleton wrote:
> In 411487 it mentions:
>
> """So, it seems it's directly related to libmhash2 (as [2] suggests)."""
>
> Disabling of mhash module may not be enough if one of the other PHP
> modules they list in 433038 also use libmhash2 library. Quite possible
> that one of the crypto libraries use it, or the ldap module mentioned
> in the mod_python mailing list mail.
>
> Can you run ldd on main php module and all php modules and see which
> one has a dependency on libmhash2, or any other md5 hash library.
In the user's last message to the bug report, he includes the contents
of /proc/.../maps for functioning and malfunctioning apache instances.
> Basic problem as we understand it is that libmhash2 uses a symbol name
> which clashes with one used by Python md5 module. Which ever gets
> loaded first, usually php version, takes precedence and since that is
> not compatible with other package a crash occurs.
>
> If it can be determined that it is libmhash2 and then which symbol in
> it clashes with one in Python md5 module, one or the other could
> somehow be namespace escaped to avoid the problem.
Is it possibly some other library than libmhash2? The only additonal
cryptography-related DSOs I see present in the user's php instance are:
/usr/lib/libmcrypt.so.4.4.7
/usr/lib/php5/20060613+lfs/mcrypt.so
All the symbols in those DSOs appear to be namespace escaped.
--
Robert Edmonds
edmonds@debian.org
|