Hi Michael,
> > http://svn.kmrc.de/download/distribution/contrib/doc/Minimal-Cyrus-SASL-Win32-HowTo.txt
>
> Many thanks for this! I don't know how persistent this link will be.
> So do you mind if I add this as-is to python-ldap's source
> distribution? In the long run we can add this in file
> D
Torsten Kurbad wrote:
>
>> I'd appreciate to have this in the official docs in a separate
>> section under
>>
>> http://www.python-ldap.org/doc/html/installing.html#building-and-installing
>
> that would be great indeed.
>
> I had very little time this morning (the internet link of our institute
Torsten Kurbad wrote:
> Hi Waldemar,
>
>> 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.
>
> unfortu
Waldemar Osuch wrote:
> 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
Hi Michael,
> I'd appreciate to have this in the official docs in a separate
> section under
>
> http://www.python-ldap.org/doc/html/installing.html#building-and-installing
that would be great indeed.
I had very little time this morning (the internet link of our institute
was broken and I had t
Torsten Kurbad wrote:
> But here's my idea: I'll put up a documentation today on what I did to
> get cyrus-sasl compiling successfully using MinGW.
I'd appreciate to have this in the official docs in a separate section under
http://www.python-ldap.org/doc/html/installing.html#building-and-install
Hi Waldemar,
> 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.
unfortunately, .dlls are relatively usele
On Wed, Aug 19, 2009 at 11:25 AM, Torsten
Kurbad 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
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_ipfromstrin
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:/p
> I'll try now to dig into the configure
> scripts of Cyrus-SASL to get rid of most of the dependencies (as the
> Mozilla guys did with the NTMakefile). Then it should be possible to
> do a "real" static build of library and plugins using MinGW.
I think, I'm almost there. I have a static libsasl a
Hi Michael,
thanks for testing the new .egg so quickly.
> Unfortunately it does not seem to work:
That's really unfortunate. I'll try now to dig into the configure
scripts of Cyrus-SASL to get rid of most of the dependencies (as the
Mozilla guys did with the NTMakefile). Then it should be possib
Torsten,
first thanks for trying to get that working.
Torsten Kurbad wrote:
>> My understanding of how it is supposed to work is that _ldap.pyd
>> calls into libsasl.dll first (this part works) but then libsasl.dll
>> has to find and load the requested auth mechanism.
Yes, that's my superficial
Hi list,
sorry for getting back to this so late, but I've been away from my
Windows development machine for a while...
> My understanding of how it is supposed to work is that _ldap.pyd
> calls into libsasl.dll first (this part works) but then libsasl.dll
> has to find and load the requested auth
Torsten Kurbad wrote:
>>> Im using the 2.3.9 release I got here:
>>> http://svn.kmrc.de/download/distribution/contrib/
>
>> These are .egg files built by Torsten. Not sure what he did regarding
>> Kerberos.
>
> Sorry for my late reply.
>
> To be honest, I did nothing regarding Kerberos. I just
Hi list,
>> Im using the 2.3.9 release I got here:
>> http://svn.kmrc.de/download/distribution/contrib/
> These are .egg files built by Torsten. Not sure what he did regarding
> Kerberos.
Sorry for my late reply.
To be honest, I did nothing regarding Kerberos. I just compiled a very
stripped d
--- Original Message
From: Waldemar Osuch
To: Michael Ströder
Cc: python-ldap-dev@lists.sourceforge.net
Sent: Thursday, 6 August, 2009 5:07:08
Subject: Re: SASL GSSAPI under Win32
2009/8/5 Michael Ströder :
> Waldemar Osuch wrote:
>> I have made a couple attempts to support SAS
2009/8/5 Michael Ströder :
> Waldemar Osuch wrote:
>> I have made a couple attempts to support SASL in the Win32 builds.
>> One user even reported a success using it but it never worked for me.
>> I will give it one more go but I can not make any promises.
>
> I tried to bind with SASL DIGEST-MD5 t
Waldemar Osuch wrote:
> I have made a couple attempts to support SASL in the Win32 builds.
> One user even reported a success using it but it never worked for me.
> I will give it one more go but I can not make any promises.
I tried to bind with SASL DIGEST-MD5 to MS AD W2K3SP2 and to OpenLDAP 2.4
2009/8/5 Michael Ströder :
> Jeroen Michiel wrote:
>>
>
> I'm pretty sure SASL bind with GSSAPI mech is not supported with the Win32
> builds. Therefore I changed the subject line to trigger attention of the
> relevant readers.
>
> The OpenLDAP libs are usually compiled against heimdal or MIT Kerb
Jeroen Michiel wrote:
>
> I'm trying to get python-ldap working on a windows machine to authenticate
> users against an Active Directory server. However, I'm getting the weirdest
> things...
>
> This is what I'm trying:
>
> import ldap, ldap.sasl
>
> conn = ldap.initialize('ldap://blabla')
> co
21 matches
Mail list logo
