On 2012-01-12 19:11:56 +0100, Philipp Kraus said: > On 2012-01-12 18:46:30 +0100, Roland Gruber said: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi Phil, >> >> Am 12.01.2012 18:32, schrieb Philipp Kraus: >>>> ok, the function will be renamed in the next release to avoid trouble >>>> with future PHP releases. >>> >>> Can I test a developer version with this changes? >> >> you can just rename all occurrences of hex2bin with "convertHex2bin" >> (the new name). There are only a few. > > That works now. I have changes the filer unde rthe lib-direcoty > account.inc, config.inc and ldap.inc > >> >> >>> I would like to test the problem with the hex2bin-change, I think >>> debugging with >>> wireshark isn't a good idea, because I use SSL connection, so I will debug >>> the >>> server process / log. >> >> There is no usage of hex2bin in the login procedure. But if you use SSL >> please check if you did not activate TLS in your LAM server profile. >> This will cause such an operations error. > > I have copy my old config-files to the new LAM directory. Cert is > correct installed and the serveradress is set to ldaps:// and TLS is > enabled. > The old config works with TLS & ldaps://
LAM shows within the log: ERROR: Unable to start TLS encryption. Please check if your server certificate is valid and if the LDAP server supports TLS at all. The cert is valid and TLS is also used by the system configuration. getent passwd / group shows the LDAP users. Permissions are also set correctly, so the webserver can read the CA cert. Dou you have any idea? Thanks Phil ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _______________________________________________ Lam-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lam-public
