Re: SASL GSSAPI under Win32
Hi list, I think, I'm almost there. I have a static libsasl and several static plugin libs, but when I try to link one of the plugins with _ldap.pyd, I get: e:\projects\prereq\built\cyrus-sasl\lib\sasl2\libcrammd5.a(plugin_common.o): In function `plug_ipfromstring': e:/projects/prereq/src/cyrus-sasl-2.1.23/plugins/plugin_common.c:150: undefined reference to `sasl_getaddrinfo' e:/projects/prereq/src/cyrus-sasl-2.1.23/plugins/plugin_common.c:157: undefined reference to `sasl_freeaddrinfo' collect2: ld returned 1 exit status error: command 'gcc' failed with exit status 1 Should be a matter of proper includes. I'll track that down tomorrow... in fact, it was a bit more than just proper includes, that's why it took me so long. ;-) But anyway, here's a new .egg for testing: http://svn.kmrc.de/download/distribution/contrib/python_ldap-2.3.9-py2.6-win32.egg Good luck and best regards, Torsten PS: Waldemar, in case it still doesn't work: Do you have IRC, ICQ, Skype or the like? -- Happiness is a positive cash flow. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Python-LDAP-dev mailing list Python-LDAP-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
Re: SASL GSSAPI under Win32
Torsten Kurbad wrote:
I think, I'm almost there. I have a static libsasl and several static
plugin libs, but when I try to link one of the plugins with
_ldap.pyd, I get:
e:\projects\prereq\built\cyrus-sasl\lib\sasl2\libcrammd5.a(plugin_common.o):
In function `plug_ipfromstring':
e:/projects/prereq/src/cyrus-sasl-2.1.23/plugins/plugin_common.c:150:
undefined reference to `sasl_getaddrinfo'
e:/projects/prereq/src/cyrus-sasl-2.1.23/plugins/plugin_common.c:157:
undefined reference to `sasl_freeaddrinfo'
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1
Should be a matter of proper includes. I'll track that down
tomorrow...
in fact, it was a bit more than just proper includes, that's why it took
me so long. ;-)
But anyway, here's a new .egg for testing:
http://svn.kmrc.de/download/distribution/contrib/python_ldap-2.3.9-py2.6-win32.egg
Sorry, still does not work. This is the console output:
U:\Proj\python-ldap\python-ldap\Democ:\Python26\python.exe sasl_bind.py
CRAM-MD5
Error using SASL mechanism CRAM-MD5 {'desc': 'Success'}
PLAIN
Error using SASL mechanism PLAIN {'desc': 'Success'}
LOGIN
Error using SASL mechanism LOGIN {'desc': 'Success'}
EXTERNAL
Error using SASL mechanism EXTERNAL {'desc': 'Success'}
GSSAPI
Error using SASL mechanism GSSAPI {'desc': 'Success'}
NTLM
Error using SASL mechanism NTLM {'desc': 'Success'}
DIGEST-MD5
Error using SASL mechanism DIGEST-MD5 {'desc': 'Success'}
BTW: You could test yourself e.g. against MS AD but take the FQDN in the LDAP
URI then.
Are there any options in cyrus-sasl to turn on debug logs? (Aargh! Tried to
use mod_auth_kerb today and the debugging also pretty much sucks with MIT
Kerberos.)
Ciao, Michael.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Python-LDAP-dev mailing list
Python-LDAP-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
Re: SASL GSSAPI under Win32
On Wed, Aug 19, 2009 at 11:25 AM, Torsten Kurbadpython-l...@tk-webart.de wrote: Hi list, But anyway, here's a new .egg for testing: http://svn.kmrc.de/download/distribution/contrib/python_ldap-2.3.9-py2.6-win32.egg Unfortunately it did not work for me either but your dedication to the cause prompted me to test my version of the build some more :) My build is not static anymore. Now I put all the required *.dll(s) into site-packages\ldap directory. I also put the _ldap.pyd in there too so the extension can find them. This approach work for all the dlls except the SASL plugins. If I put the SASL plugin dlls into into C:\CMU\bin\sasl2 then they will be found. In my environment only DIGEST-MD5 and NTLM got loaded but NTLM did not work. I have got 'Authentication method not supported' error. Now the question is, should I continue to pretend that SASL mechanisms are supported? Are the 2 or rather 1.5 available mechanisms worth the effort? I hope Torsten will be successful but I feel ready to give up on SASL support in my builds. They never really worked out of the box anyway. If you are depending on existing SASL support in my builds it is time to speak up. Unless Torsten is successful, the 2.3.9 build will not have it. Waldemar -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Python-LDAP-dev mailing list Python-LDAP-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
