python-ldap-dev — discussion among developers

Re: change password for user

[Zhang H. <zhb...@gm...>]

Michael Ströder wrote:
> Yes. Other LDAP servers might have a different configuration. Also some
> servers set other password attributes as well (e.g. the smbk5pwd overlay
> for OpenLDAP sets Samba password attributes and the Kerberos keys for a
> heimdal KDC).
>
> Ciao, Michael.
>
>   

Thanks Michael. :)

How can i set DEFAULT password-hash in slapd.conf? such as MD5 or whatever.


-- 
Best regards.

Zhang Huangbin

- Open Source Mail Server Solution for RHEL/CentOS 5.x:
  http://code.google.com/p/iredmail/

Re: change password for user

[Michael S. <mi...@st...>]

Zhang Huangbin wrote:
> Michael Ströder wrote:
>>> so it would be nice to have
>>> the directory server do the hashing instead. I've found the
>>> method:
>>>
>>>     passwd_s(user, oldpw, newpw, [serverctrls=None, [clientctrls=None]])
>>>
>>> but are there any way to use that when I don't know the plaintext
>>> 'oldpw' ?
>>>     
>>
>> Simply use None for oldpw.
> 
> How can i specfy hash mechanism in passwd_s()? like SSHA, MD5.

You don't. That's completely configured at the server's side.

> It seems use default setting of ldap server (password-hash in openldap
> slapd.conf),

Yes. Other LDAP servers might have a different configuration. Also some
servers set other password attributes as well (e.g. the smbk5pwd overlay
for OpenLDAP sets Samba password attributes and the Kerberos keys for a
heimdal KDC).

Ciao, Michael.

Re: change password for user

[Zhang H. <zhb...@gm...>]

Michael Ströder wrote:
>> so it would be nice to have
>> the directory server do the hashing instead. I've found the
>> method:
>>
>> 	passwd_s(user, oldpw, newpw, [serverctrls=None, [clientctrls=None]])
>>
>> but are there any way to use that when I don't know the plaintext
>> 'oldpw' ?
>>     
>
> Simply use None for oldpw.

How can i specfy hash mechanism in passwd_s()? like SSHA, MD5.
It seems use default setting of ldap server (password-hash in openldap 
slapd.conf),
right?

-- 
Best regards.

Zhang Huangbin

- Open Source Mail Server Solution for RHEL/CentOS 5.x:
  http://code.google.com/p/iredmail/

Re: change password for user

[Michael S. <mi...@st...>]

Jan-Frode Myklebust wrote:
> I have a script that tries to sync a userdatabase with
> plaintext username/password in mysql, to a Centos Directory
> Server. Currently I've been pushing the passwords into the
> directory by first creating the SSHA1 hash in python and
> store '{SSHA}' + encode-string in the password field.
> 
> But, it occurred to me that I'm not fully sure what I'm doing 
> when creating the SSHA1 hash,

If the password is usable afterwards there's nothing wrong with
client-side password hashing. The salt should be at least 4 bytes long.

> so it would be nice to have
> the directory server do the hashing instead. I've found the
> method:
> 
> 	passwd_s(user, oldpw, newpw, [serverctrls=None, [clientctrls=None]])
> 
> but are there any way to use that when I don't know the plaintext
> 'oldpw' ?

Simply use None for oldpw.

Ciao, Michael.

change password for user

[Jan-Frode M. <jan...@ta...>]

I have a script that tries to sync a userdatabase with
plaintext username/password in mysql, to a Centos Directory
Server. Currently I've been pushing the passwords into the
directory by first creating the SSHA1 hash in python and
store '{SSHA}' + encode-string in the password field.

But, it occurred to me that I'm not fully sure what I'm doing 
when creating the SSHA1 hash, so it would be nice to have
the directory server do the hashing instead. I've found the
method:

	passwd_s(user, oldpw, newpw, [serverctrls=None, [clientctrls=None]])

but are there any way to use that when I don't know the plaintext
'oldpw' ?


  -jf

Re: ldap.ENCODING_ERROR when trying to use SimplePageResultsControl (pyldap: message 1 of 20)

[<pyl...@ne...>]

Michael,

I will try as you suggested and will compile the current versions of
openldap, python-ldap, cyrus-sasl, and openssl without any patches and
default options. I'll let you know how that turns out.

To respond to your point that you don't know what build options are
used, or what patches applied to binary distributions, here is what
the spec files I used to build openldap and python-ldap contained:
python-ldap only had one patch applied to it. I'll paste the patch
below, but the patch isn't the problem. I recompiled the python-ldap
RPM without any of the patches and ran into the same encoding error.

The packages was configured and built using the following two commands:
setup.py build
setup.py install --skip-build --root $RPM_BUILD_ROOT
($RPM_BUILD_ROOT being /var/tmp/python-ldap-2.3.5-root )

python-ldap-2.2.0-dirs.patch:
--- python-ldap-2.3.5/setup.cfg.dirs    2008-07-06 11:04:13.000000000 -0400
+++ python-ldap-2.3.5/setup.cfg 2008-09-03 13:45:20.000000000 -0400
@@ -2,8 +2,7 @@
 extra_objects =
 extra_compile_args =
 libs = ldap_r lber sasl2 ssl crypto
-library_dirs = /usr/local/openldap-2.3/lib
-include_dirs = /usr/local/openldap-2.3/include /usr/include/sasl
+include_dirs = /usr/include/sasl

OpenLDAP was built with considerably more patches and the build
process is extremely involved.
The following flags are used in building:
CFLAGS=" -D_REENTRANT -fPIC -D_GNU_SOURCE"

The OpenLDAP package RPM builds its own version of BerkeleyDB which it
builds like so:
configure -C \
    --with-pic \
    --disable-static \
    --enable-shared \
    --with-uniquename=_openldap_slapd_46 \
    --prefix=${dbdir} \
    --includedir=${dbdir}/include \
    --libdir=${dbdir}/%{_lib}${subdir:+/${subdir}}

make %{_smp_mflags} libdb_base=libslapd_db libso_base=libslapd_db
make install libdb_base=libslapd_db libso_base=libslapd_db strip="false"

OpenLDAP is configured and made with the following flags:
configure \
    --with-threads=posix \
    --enable-local --enable-rlookups \
    --with-tls \
    --with-cyrus-sasl \
    --enable-wrappers \
    --enable-passwd \
    --enable-cleartext \
    --enable-crypt \
    --enable-spasswd \
    --enable-lmpasswd \
    --enable-modules \
    --disable-sql \
    --libexecdir=%{_libdir} \
    $@
make %{_smp_mflags} LIBTOOL="$libtool"

The openldap clients are build using:
build \
    --disable-slapd \
    --enable-shared \
    --enable-dynamic \
    --enable-static \
    --without-kerberos \
    --with-pic



If there's any information you need to figure out what's going, let me
know and I'll be happy to grab it for you.

Dominic

On Thu, Mar 5, 2009 at 6:22 AM, Michael Ströder - mi...@st...
<+pyldap+dlobue+63e3ab027f.michael#str...@sp...>
wrote:
> pyl...@ne... wrote:
>>
>> I've run into the same problem as Joel on basically an identical setup
>> - CentOS 5.2, openldap 2.3.27-8.el5_2.4, python 2.4.3-21.el5,
>> python-ldap 2.2.0-2.1. This of course being on a 64 bit release of
>> CentOS.
>>
>> I did as you suggested and updated openldap to 2.4.12-1, and
>> python-ldap to 2.3.5-1, but I still received the exact same error.
>
> The problem with using binary packages is that I never know whether
> patches were applied by the distributor and which build parameters were
> used.
>
> Also note there's python-ldap with some minor build fixes and OpenLDAP
> 2.4.15 with numerous fixes to libldap. OpenLDAP developers will likely
> not give support with this issue if the problem cannot be reproduced
> with recent code.
>
>> Because you mentioned that you had never tested python-ldap on a 64
>> bit machine, I duplicated my setup in a VirtualBox VM only using a
>> i686 release of CentOS rather than x64.
>>
>> I ran my python program using the old versions of software ( openldap
>> 2.3.27-8.el5_2.4, python 2.4.3-21.el5, python-ldap 2.2.0-2) and it ran
>> without any problems whatsoever.
>
> Thanks for testing this.
>
>> Any suggestions on how to fix this?
>
> At the moment I have no idea how to proceed. I'd suggest to build from
> source. Not sure about compiler woes on that platform. E.g. try turning
> off optimization (with option -O0) when building from source.
>
> Ciao, Michael.
>

Re: ldap.ENCODING_ERROR when trying to use SimplePageResultsControl

[Michael S. <mi...@st...>]

pyl...@ne... wrote:
> 
> I've run into the same problem as Joel on basically an identical setup
> - CentOS 5.2, openldap 2.3.27-8.el5_2.4, python 2.4.3-21.el5,
> python-ldap 2.2.0-2.1. This of course being on a 64 bit release of
> CentOS.
> 
> I did as you suggested and updated openldap to 2.4.12-1, and
> python-ldap to 2.3.5-1, but I still received the exact same error.

The problem with using binary packages is that I never know whether
patches were applied by the distributor and which build parameters were
used.

Also note there's python-ldap with some minor build fixes and OpenLDAP
2.4.15 with numerous fixes to libldap. OpenLDAP developers will likely
not give support with this issue if the problem cannot be reproduced
with recent code.

> Because you mentioned that you had never tested python-ldap on a 64
> bit machine, I duplicated my setup in a VirtualBox VM only using a
> i686 release of CentOS rather than x64.
> 
> I ran my python program using the old versions of software ( openldap
> 2.3.27-8.el5_2.4, python 2.4.3-21.el5, python-ldap 2.2.0-2) and it ran
> without any problems whatsoever.

Thanks for testing this.

> Any suggestions on how to fix this?

At the moment I have no idea how to proceed. I'd suggest to build from
source. Not sure about compiler woes on that platform. E.g. try turning
off optimization (with option -O0) when building from source.

Ciao, Michael.

RE: ldap.ENCODING_ERROR when trying to use SimplePageResultsControl

[<pyl...@ne...>]

Michael,

I've run into the same problem as Joel on basically an identical setup
- CentOS 5.2, openldap 2.3.27-8.el5_2.4, python 2.4.3-21.el5,
python-ldap 2.2.0-2.1. This of course being on a 64 bit release of
CentOS.

I did as you suggested and updated openldap to 2.4.12-1, and
python-ldap to 2.3.5-1, but I still received the exact same error.

Because you mentioned that you had never tested python-ldap on a 64
bit machine, I duplicated my setup in a VirtualBox VM only using a
i686 release of CentOS rather than x64.

I ran my python program using the old versions of software ( openldap
2.3.27-8.el5_2.4, python 2.4.3-21.el5, python-ldap 2.2.0-2) and it ran
without any problems whatsoever.

Any suggestions on how to fix this?

Let me know if you need any other info.

Dominic

-----------------------------
Joel Heenan wrote:
> Hi Michael,
>
> Comments inline:
>
>> Michael Ströder wrote:
>> Joel Heenan wrote:
>>
>>> File "/usr/lib64/python2.4/site-packages/ldap/controls.py", line
>> 78,
>>> in encodeControlValue
>>>
>>> return _ldap.encode_page_control(size,cookie)
>>>
>>> ldap.ENCODING_ERROR
>> It seems you're running on a 64-bit platform. I did never test
>> python-ldap on such a system. Which version of python-ldap is it? Did
>> you compile it yourself? Which versions of OpenLDAP libs are used?
>
> I am using 64-bit RPM's compiled by RedHat for RHEL5.2 . The 32-bit
> variants are installed I'll see if I can work out how to force it to
> use them.
>
> Here are the versions involved, but be aware RedHat versions include
> backporting so it can be difficult to say exactly what is included:
>
> openldap-2.3.27-8.el5_1.3
> openldap-devel-2.3.27-8.el5_1.3
> python-ldap-2.2.0-2.1

These releases are old:
OpenLDAP 2.3.27 was released 2006-08-19
python-ldap 2.2.0 was released 2006-04-10

There have been numerous bug fixes to both packages since then. While I
don't have a 64-bit box myself there were several related fixes
contributed and tested by others. So I suggest to build recent releases
of both from source and test with that.

>>> Server is RHEL5.2
>> Hmm, isn't this quite old? I'd guess old versions of python-ldap and
>> OpenLDAP are shipped with this release.
>
> Err RHEL5.2 is the latest stable I believe.

Whatever stable means to Red Hat for these particular packages. Sorry,
if you insist on using these ancient versions I have to point you to Red
Hat's support.

Ciao, Michael.

Re: ldap.ENCODING_ERROR when trying to use SimplePageResultsControl

[Russell J. <ra...@cs...>]

Michael Ströder wrote:
> It seems you're running on a 64-bit platform. I did never test
> python-ldap on such a system. Which version of python-ldap is it? Did
> you compile it yourself? Which versions of OpenLDAP libs are used?
> 

Just as a data point, I've been running python-ldap (from ports) on FreeBSD-amd64 since
6.x without issue.

-- 
Russell A. Jackson <ra...@cs...>
Network Analyst
California State University, Bakersfield

Q:	What do they call the alphabet in Arkansas?
A:	The impossible dream.

Re: ldap.ENCODING_ERROR when trying to use SimplePageResultsControl

[Michael S. <mi...@st...>]

Joel Heenan wrote:
> Hi Michael,
> 
> Comments inline:
> 
>> Michael Ströder wrote:
>> Joel Heenan wrote:
>>
>>>   File "/usr/lib64/python2.4/site-packages/ldap/controls.py", line
>> 78,
>>> in encodeControlValue
>>>
>>>     return _ldap.encode_page_control(size,cookie)
>>>
>>> ldap.ENCODING_ERROR
>> It seems you're running on a 64-bit platform. I did never test
>> python-ldap on such a system. Which version of python-ldap is it? Did
>> you compile it yourself? Which versions of OpenLDAP libs are used?
> 
> I am using 64-bit RPM's compiled by RedHat for RHEL5.2 . The 32-bit
> variants are installed I'll see if I can work out how to force it to
> use them.
> 
> Here are the versions involved, but be aware RedHat versions include
> backporting so it can be difficult to say exactly what is included:
> 
> openldap-2.3.27-8.el5_1.3
> openldap-devel-2.3.27-8.el5_1.3
> python-ldap-2.2.0-2.1

These releases are old:
OpenLDAP 2.3.27 was released 2006-08-19
python-ldap 2.2.0 was released 2006-04-10

There have been numerous bug fixes to both packages since then. While I
don't have a 64-bit box myself there were several related fixes
contributed and tested by others. So I suggest to build recent releases
of both from source and test with that.

>>> Server is RHEL5.2
>> Hmm, isn't this quite old? I'd guess old versions of python-ldap and
>> OpenLDAP are shipped with this release.
> 
> Err RHEL5.2 is the latest stable I believe.

Whatever stable means to Red Hat for these particular packages. Sorry,
if you insist on using these ancient versions I have to point you to Red
Hat's support.

Ciao, Michael.

RE: ldap.ENCODING_ERROR when trying to use SimplePageResultsControl

[Joel H. <Joe...@Op...>]

Hi Michael,

Comments inline:

> Michael Ströder wrote:
> Joel Heenan wrote:
>
> >   File "/usr/lib64/python2.4/site-packages/ldap/controls.py", line
> 78,
> > in encodeControlValue
> >
> >     return _ldap.encode_page_control(size,cookie)
> >
> > ldap.ENCODING_ERROR
>
> It seems you're running on a 64-bit platform. I did never test
> python-ldap on such a system. Which version of python-ldap is it? Did
> you compile it yourself? Which versions of OpenLDAP libs are used?
>

I am using 64-bit RPM's compiled by RedHat for RHEL5.2 . The 32-bit variants are installed I'll see if I can work out how to force it to use them.

Here are the versions involved, but be aware RedHat versions include backporting so it can be difficult to say exactly what is included:

openldap-2.3.27-8.el5_1.3
openldap-devel-2.3.27-8.el5_1.3
python-ldap-2.2.0-2.1

> > Server is RHEL5.2
>
> Hmm, isn't this quite old? I'd guess old versions of python-ldap and
> OpenLDAP are shipped with this release.

Err RHEL5.2 is the latest stable I believe. RHEL5.3 may have been released. Not to be confused with RedHat 5.2 which is of course ancient :-)

Joel

Information contained in this communication (including any attachments) is confidential and may be privileged or subject to copyright.  If you have received this communication in error you are not authorised to use the information in any way and Optiver requests that you notify the sender by return email, destroy all copies and delete the information from your system.  Optiver does not represent, warrant or guarantee that this communication is free from computer viruses or other defects or that the integrity of this communication has been maintained.  Any views expressed in this communication are those of the individual sender.  Optiver does not accept liability for any loss or damage caused directly or indirectly by this communication or its use.

Please consider the environment before printing this email.

Re: ldap.ENCODING_ERROR when trying to use SimplePageResultsControl

[Michael S. <mi...@st...>]

Joel Heenan wrote:
> 
> I'm trying to use SimplePagedResultsControl so I can pull some data out
> of Active Directory that has a Server-Limit set. I got most of my code
> from this guide http://www.novell.com/coolsolutions/tip/18274.html

Since I posted this code I think it works. ;-)

>   File "/usr/lib64/python2.4/site-packages/ldap/controls.py", line 78,
> in encodeControlValue
> 
>     return _ldap.encode_page_control(size,cookie)
> 
> ldap.ENCODING_ERROR

It seems you're running on a 64-bit platform. I did never test
python-ldap on such a system. Which version of python-ldap is it? Did
you compile it yourself? Which versions of OpenLDAP libs are used?

> Server is RHEL5.2

Hmm, isn't this quite old? I'd guess old versions of python-ldap and
OpenLDAP are shipped with this release.

Ciao, Michael.

ldap.ENCODING_ERROR when trying to use SimplePageResultsControl

[Joel H. <Joe...@Op...>]

I'm trying to use SimplePagedResultsControl so I can pull some data out of Active Directory that has a Server-Limit set. I got most of my code from this guide http://www.novell.com/coolsolutions/tip/18274.html

When I try and run it I get this dump:

"""
SimplePagedResultsControl(1.2.840.113556.1.4.319,True,(10, ''))
Traceback (most recent call last):
  File "./test_ldap_brakeit.py", line 29, in ?
    msgid = l.search_ext(base, ldap.SCOPE_SUBTREE, 'objectclass=user', serverctrls=[lc])
  File "/usr/lib64/python2.4/site-packages/ldap/ldapobject.py", line 468, in search_ext
    EncodeControlTuples(serverctrls),
  File "/usr/lib64/python2.4/site-packages/ldap/controls.py", line 93, in EncodeControlTuples
    result = [
  File "/usr/lib64/python2.4/site-packages/ldap/controls.py", line 45, in getEncodedTuple
    return (self.controlType,self.criticality,self.encodeControlValue(self.controlValue))
  File "/usr/lib64/python2.4/site-packages/ldap/controls.py", line 78, in encodeControlValue
    return _ldap.encode_page_control(size,cookie)
ldap.ENCODING_ERROR
"""

Server is RHEL5.2 , not too sure about the Active Directory I think it is running on Windows Server 2003.

Here is the code:

#!/usr/bin/python
#

import ldap,ldap.async,pprint
from ldap.controls import SimplePagedResultsControl

server       = 'xxxx.com'
ldap_version = 3
base         = 'dc=example,dc=com'
binddn       = ''
bindpw       = ''
userbase     = ''
port         = 3268
page_size    = 10

l = ldap.open(server,port)
l.protocol_version = ldap_version
l.simple_bind_s(binddn, bindpw)
ldap.set_option(ldap.OPT_REFERRALS, 0)

lc = SimplePagedResultsControl(
        ldap.LDAP_CONTROL_PAGE_OID, True, (page_size,'') )

print lc

msgid = l.search_ext(base, ldap.SCOPE_SUBTREE, 'objectclass=user', serverctrls=[lc])

pages = 0
while True:
        pages += 1
        print "Getting page %d" % (pages,)
        rtype,rdata,rmsgid,serverctrls = l.result3(msgid)
        print "%d results" % len(rdata)
        pctrls = [ c for c in serverctrls if c.controlType == ldap.LDAP_CONTROL_PAGE_OID ]
        if pctrls:
                est, cookie = pctrls[0].controlValue
                if cookie:
                        lc.controlValue = (page_size,cookie)
                        msgid = l.search_ext(base, ldap.SCOPE_SUBTREE, 'objectclass=user', serverctrls=[lc])
                else:
                        break
        else:
                print "Warning: Server ignores RFC 2696 control"

Joel Heenan


________________________________
Information contained in this communication (including any attachments) is confidential and may be privileged or subject to copyright. If you have received this communication in error you are not authorised to use the information in any way and Optiver requests that you notify the sender by return email, destroy all copies and delete the information from your system. Optiver does not represent, warrant or guarantee that this communication is free from computer viruses or other defects or that the integrity of this communication has been maintained. Any views expressed in this communication are those of the individual sender. Optiver does not accept liability for any loss or damage caused directly or indirectly by this communication or its use.

Please consider the environment before printing this email.

Re: Distinguished name problem

[Michael S. <mi...@st...>]

Fredrik Melander wrote:
> first of all - I noticed (a bit too late) that this actually is the
> developer-list (although a user-list doesn't seem to exist). I want to
> take the opportunity to thank you for taking time to answer my trivial
> questions in spite of this. Much appreciated!

There's only one low-traffic mailing list python-ldap-dev and therefore
also beginner questions are welcome there. Keep posting questions there.

>> Which documentation? ldap_get_dn() is part of the underlying libldap and
>> you don't have to mess with that yourself.
>>   
> Well, I was referring to the the downloadable pdf at Sourceforge
> (version 2.3.2) which contains this statement:
> "The DN in /dn /is extracted using the underlying ldap_get_dn()
> function, which may raise an exception if the DN is malformed."
> Although admittedly the use of the word "underlying" kind of hinted
> that I wouldn't have to touch this myself, I got a bit confused by
> this...

Hmm, I tried to fix the wording a little bit. Not sure whether that
helps avoiding confusion though.

Ciao, Michael.

Re: Distinguished name problem

[Michael S. <mi...@st...>]

Fredrik Melander wrote:
> From the command line (ldapsearch) I've got no problem becoming whatever
> I want. The python-ldap module on the other hand gives me *almost*
> anything I want. The only thing that I seem to not be able to get is the
> DN.

The 2-tuples returned by ldap_search_s() etc. are (dn,entry) where entry
is the dictionary {attrtype:[attrvalues]} and dn is simply a binary
string containing the entry's distinguished name.

See also:

http://python-ldap.sourceforge.net/doc/html/ldap.html#example

> The documentation makes a somewhat cryptic reference to a function
> called ldap_get_dn().

Which documentation? ldap_get_dn() is part of the underlying libldap and
you don't have to mess with that yourself.

Ciao, Michael.

Distinguished name problem

[Fredrik M. <mel...@df...>]

Hello, list!
I'm sure I'm overlooking something fairly obvious her, and I'm hoping
that somebody here can point me in the right direction. We have a small
ldap-server running here and I've now been given the honor of writing a
small Python program to interact with it.

>From the command line (ldapsearch) I've got no problem becoming whatever
I want. The python-ldap module on the other hand gives me *almost*
anything I want. The only thing that I seem to not be able to get is the
DN. The documentation makes a somewhat cryptic reference to a function
called ldap_get_dn(). It's mentioned only once and not further
explained. Trial and error, excessive googling, book flipping etc.
unfortunately didn't get me any further either.

Bear with me if this is a stupid question. I, as a programmer, have very
limited ldap-experience (in fact, this is the first time I'm having
anything to do with it), and my ldap guru here has little programming
experience, so we're kind of stuck at the moment.

Any suggestions very welcome! Thanks in advance.

Regards,
Fredrik

Re: Updated eggs for linux x86 and amd64

[Michael S. <mi...@st...>]

Sidnei da Silva wrote:
> On Thu, Jan 29, 2009 at 5:43 PM, Waldemar Osuch
> <wal...@gm...> wrote:
>> On Thu, Jan 29, 2009 at 1:17 AM, Torsten Kurbad
>> <pyt...@tk...> wrote:
>>> On Thursday, January 29, 2009 at 03:44 Sidnei da Silva wrote:
>>>> The best way really would be to build it statically. I did manage to
>>>> do this *once*, but fail to remember how. I'm sure it is possible
>>>> though.
>>> Yes, that's definitely a good idea. I'll try to accomplish this. If I'm
>>> stuck somewhere, maybe we can explore your memory together? ;-)
>>>
>> To force static build of the extensions I tweak source of
>> distutils/cygwinccompiler.py
>> After lineno 299 I have added:
>>
>> #TODO enable to force static build
>> if False:
>>    shared_option = "-mdll -static"
>>
>> and change "False" into "True" whenever I build python-ldap.
>> It seems to work.
>>
>> If you find a more elegant way of doing it please share.
> 
> Yes, that rings a bell. I think I managed to pass those flags manually
> without hacking the distutils source, but that's exactly what needs to
> be done.

Feel free to post a patch to setup.py / setup.cfg which does that.

Ciao, Michael.

Re: Re[2]: Updated eggs for linux x86 and amd64

[Sidnei da S. <si...@en...>]

On Thu, Jan 29, 2009 at 5:43 PM, Waldemar Osuch
<wal...@gm...> wrote:
> On Thu, Jan 29, 2009 at 1:17 AM, Torsten Kurbad
> <pyt...@tk...> wrote:
>> On Thursday, January 29, 2009 at 03:44 Sidnei da Silva wrote:
>>> The best way really would be to build it statically. I did manage to
>>> do this *once*, but fail to remember how. I'm sure it is possible
>>> though.
>>
>> Yes, that's definitely a good idea. I'll try to accomplish this. If I'm
>> stuck somewhere, maybe we can explore your memory together? ;-)
>>
>
> To force static build of the extensions I tweak source of
> distutils/cygwinccompiler.py
> After lineno 299 I have added:
>
> #TODO enable to force static build
> if False:
>    shared_option = "-mdll -static"
>
> and change "False" into "True" whenever I build python-ldap.
> It seems to work.
>
> If you find a more elegant way of doing it please share.

Yes, that rings a bell. I think I managed to pass those flags manually
without hacking the distutils source, but that's exactly what needs to
be done. Thanks for refreshing my memory!

-- 
Sidnei da Silva

Re: Re[2]: Updated eggs for linux x86 and amd64

[Waldemar O. <wal...@gm...>]

On Thu, Jan 29, 2009 at 1:17 AM, Torsten Kurbad
<pyt...@tk...> wrote:
> On Thursday, January 29, 2009 at 03:44 Sidnei da Silva wrote:
>
>> <snip, re: distributing Windows deps>
>>> Does anyone have a great idea on how to accomplish that (besides
>>> giving away a zip file that has to be manually unpacked to a proper
>>> location)?
>
>> The best way really would be to build it statically. I did manage to
>> do this *once*, but fail to remember how. I'm sure it is possible
>> though.
>
> Yes, that's definitely a good idea. I'll try to accomplish this. If I'm
> stuck somewhere, maybe we can explore your memory together? ;-)
>

FYI

To force static build of the extensions I tweak source of
distutils/cygwinccompiler.py
After lineno 299 I have added:

#TODO enable to force static build
if False:
    shared_option = "-mdll -static"

and change "False" into "True" whenever I build python-ldap.
It seems to work.

If you find a more elegant way of doing it please share.

Waldemar Osuch
http://www.osuch.org

Re[2]: Updated eggs for linux x86 and amd64

[Torsten K. <pyt...@tk...>]

On Thursday, January 29, 2009 at 03:44 Sidnei da Silva wrote:

> <snip, re: distributing Windows deps>
>> Does anyone have a great idea on how to accomplish that (besides
>> giving away a zip file that has to be manually unpacked to a proper
>> location)?

> The best way really would be to build it statically. I did manage to
> do this *once*, but fail to remember how. I'm sure it is possible
> though.

Yes, that's definitely a good idea. I'll try to accomplish this. If I'm
stuck somewhere, maybe we can explore your memory together? ;-)

Best regards,
Torsten
-- 
Never make anything simple and efficient when a way can be found to
make it complex and wonderful.              - Murphy's Law No. 13 -

Re:

[Michael S. <mi...@st...>]

sol...@em... wrote:
> 
> I tried using the platform install and for some reason I get this error.
> ImportError: ld.so.1: python: fatal: libresolv.so.2: open failed: No such file or directory
> 
> Also I ran ldd on the libresolve.so.2
> libresolv.so.2 =>        /usr/lib/libresolv.so.2
> libresolv.so.2 (SUNW_2.2.2) =>   (version not found)

That's probably item 9 in the FAQ:

http://python-ldap.sourceforge.net/faq.shtml

Ciao, Michael.

Updated eggs for linux x86 and amd64

[Torsten K. <pyt...@tk...>]

Hi folks,

it's been a while since my last update, but today I built some eggs of
python-ldap 2.3.5 for Linux i686 and x86_64 and Python versions 2.4
through 2.6.
Windows and OS X versions will follow as soon as my respective
development environments are up to date and running again.

As usual, the eggs can be obtained from
http://svn.kmrc.de/download/distribution

They are built against OpenLDAP 2.3.43/OpenSSL 0.9.8j/Cyrus SASL 2.1.22

I'm still looking for a satisfactory solution to present an all-in-one
package for Windows, containing all necessary dependencies (i.e.
OpenLDAP, OpenSSL, Heimdal/MIT-Krb5, ...)
Does anyone have a great idea on how to accomplish that (besides
giving away a zip file that has to be manually unpacked to a proper
location)?

Best regards,
Torsten
-- 
Life is cheap, but the accessories can kill you.

RE:

[<sol...@em...>]

Hello all, 

I tried using the platform install and for some reason I get this error.
ImportError: ld.so.1: python: fatal: libresolv.so.2: open failed: No such file or directory


Also I ran ldd on the libresolve.so.2
libresolv.so.2 =>        /usr/lib/libresolv.so.2
libresolv.so.2 (SUNW_2.2.2) =>   (version not found)

Any of you have a clue about this?

Regards, 
Antoine	 

-----Original Message-----
From: Michael Ströder [mailto:mi...@st...] 
Sent: Monday, January 26, 2009 8:10 PM
To: Solomon, Antoine; pyt...@li...
Subject: Re: 

sol...@em... wrote:
> 
> I wanted to know if any of you were successful in getting python-ldap
> installed on solaris 10.  if so could you point me to any instructions
> that you might have?

I've installed it with the usual platform-independent method:

http://python-ldap.sourceforge.net/doc/html/installing.html

Don't know whether there are acceptable pre-built Solaris 10 packages.
You could check out the usual repositories.

Ciao, Michael.

RE:

[<sol...@em...>]

Michael, 

thanks for the info.  I will try to use this site below. 

regards, 
Antoine


-----Original Message-----
From: Michael Ströder [mailto:mi...@st...]
Sent: Mon 1/26/2009 8:10 PM
To: Solomon, Antoine; pyt...@li...
Subject: Re: 
 
sol...@em... wrote:
> 
> I wanted to know if any of you were successful in getting python-ldap
> installed on solaris 10.  if so could you point me to any instructions
> that you might have?

I've installed it with the usual platform-independent method:

http://python-ldap.sourceforge.net/doc/html/installing.html

Don't know whether there are acceptable pre-built Solaris 10 packages.
You could check out the usual repositories.

Ciao, Michael.

Re:

[Michael S. <mi...@st...>]

sol...@em... wrote:
> 
> I wanted to know if any of you were successful in getting python-ldap
> installed on solaris 10.  if so could you point me to any instructions
> that you might have?

I've installed it with the usual platform-independent method:

http://python-ldap.sourceforge.net/doc/html/installing.html

Don't know whether there are acceptable pre-built Solaris 10 packages.
You could check out the usual repositories.

Ciao, Michael.