From jerome.wax at linbox.com Tue Jul 5 17:27:45 2005 From: jerome.wax at linbox.com (=?ISO-8859-1?Q?J=E9r=F4me_Wax?=) Date: Tue, 05 Jul 2005 17:27:45 +0200 Subject: how can i delete objectclass with it's attributes Message-ID: <42CAA6F1.8050809@linbox.com> Hi, I just try to delete an objectClass. Can Python-Ldap delete attributes which corresponds to that objectClass automatically ? From francois.beretti at free.fr Tue Jul 5 17:34:12 2005 From: francois.beretti at free.fr (=?ISO-8859-1?Q?Fran=E7ois_Beretti?=) Date: Tue, 05 Jul 2005 17:34:12 +0200 Subject: how can i delete objectclass with it's attributes In-Reply-To: <42CAA6F1.8050809@linbox.com> References: <42CAA6F1.8050809@linbox.com> Message-ID: <42CAA874.2000603@free.fr> Hi Jer?me, You are not very clear on what you are trying to do... Do you mean you want to remove an objectClass from the schema of the server, or you want to remove an objectclass from an entry of the directory ? Fran?ois J?r?me Wax wrote: > Hi, > > I just try to delete an objectClass. > Can Python-Ldap delete attributes which corresponds to that > objectClass automatically ? > > > > > From francois.beretti at free.fr Tue Jul 5 17:52:03 2005 From: francois.beretti at free.fr (=?ISO-8859-1?Q?Fran=E7ois_Beretti?=) Date: Tue, 05 Jul 2005 17:52:03 +0200 Subject: how can i delete objectclass with it's attributes In-Reply-To: <42CAAA26.1000601@linbox.com> References: <42CAA6F1.8050809@linbox.com> <42CAA874.2000603@free.fr> <42CAAA26.1000601@linbox.com> Message-ID: <42CAACA3.1050706@free.fr> No, I don't think so, you have to remove the objectClass value and all the attributes values in the same modify operation. Fran?ois P.S.: don't forget to reply to all, so as the list can see your reply. J?r?me Wax wrote: > Fran?ois Beretti a ?crit : > > Sorry, can Python-Ldap can remove a schema of the server ? > > No,no, it's just to remove an objectClass on an entry of the directory > with all attributes. From jean-marc.pouchoulon at ac-montpellier.fr Thu Jul 7 17:57:15 2005 From: jean-marc.pouchoulon at ac-montpellier.fr (jean-marc.pouchoulon at ac-montpellier.fr) Date: Thu, 07 Jul 2005 17:57:15 +0200 Subject: auth with python-ldap Message-ID: <42CD50DB.1040706@ac-montpellier.fr> Helo, I'de like to autorize a user to go into a web application. anonymous bind is allowing, also a bind is always sucessfull. How can I test if a user is valid with simplebind ? ldapserver = sun directory server 5.2 passwd use shadow any examples or best pratices are welcome thanks From michael at stroeder.com Thu Jul 7 18:22:47 2005 From: michael at stroeder.com (=?ISO-8859-1?Q?Michael_Str=F6der?=) Date: Thu, 07 Jul 2005 18:22:47 +0200 Subject: auth with python-ldap In-Reply-To: <42CD50DB.1040706@ac-montpellier.fr> References: <42CD50DB.1040706@ac-montpellier.fr> Message-ID: <42CD56D7.1010609@stroeder.com> jean-marc.pouchoulon at ac-montpellier.fr wrote: > I'de like to autorize a user to go into a web application. > anonymous bind is allowing, also a bind is always sucessfull. > How can I test if a user is valid with simplebind ? You simply bind with the user's DN and his password. > ldapserver = sun directory server 5.2 > passwd use shadow Your local system's password checking is not relevant. Basically one sets the userPassword value in the user's entry. Ciao, Michael. From jerome.wax at linbox.com Wed Jul 20 11:09:43 2005 From: jerome.wax at linbox.com (=?ISO-8859-1?Q?J=E9r=F4me_Wax?=) Date: Wed, 20 Jul 2005 11:09:43 +0200 Subject: retrieves attributes from schema In-Reply-To: <42CAACA3.1050706@free.fr> References: <42CAA6F1.8050809@linbox.com> <42CAA874.2000603@free.fr> <42CAAA26.1000601@linbox.com> <42CAACA3.1050706@free.fr> Message-ID: <42DE14D7.8040101@linbox.com> Can I retrieve all required and sufficient attributes for a specific schema with Python-Ldap ? For example I need all attributes of OXUserObject schema to correctly delete OXUserObject in objectClass attribute of this user. thanks in advance. From michael at stroeder.com Wed Jul 20 11:36:41 2005 From: michael at stroeder.com (=?ISO-8859-1?Q?Michael_Str=F6der?=) Date: Wed, 20 Jul 2005 11:36:41 +0200 Subject: retrieves attributes from schema In-Reply-To: <42DE14D7.8040101@linbox.com> References: <42CAA6F1.8050809@linbox.com> <42CAA874.2000603@free.fr> <42CAAA26.1000601@linbox.com> <42CAACA3.1050706@free.fr> <42DE14D7.8040101@linbox.com> Message-ID: <42DE1B29.3050205@stroeder.com> J?r?me Wax wrote: > Can I retrieve all required and sufficient attributes for a specific > schema with Python-Ldap ? There's a undocumented module ldap.schema. See Demo/schema.py for a couple of examples. But first you should understand all the nits and bits about correct usage of LDAPv3 subschema subentries. Note: The API of ldap.schema might change in the future. I.e. I'm still thinking about changing the ill-designed error handling for non-existent schema elements. Ciao, Michael. From jerome.wax at linbox.com Wed Jul 20 14:15:59 2005 From: jerome.wax at linbox.com (=?ISO-8859-1?Q?J=E9r=F4me_Wax?=) Date: Wed, 20 Jul 2005 14:15:59 +0200 Subject: retrieves attributes from schema In-Reply-To: <42DE1B29.3050205@stroeder.com> References: <42CAA6F1.8050809@linbox.com> <42CAA874.2000603@free.fr> <42CAAA26.1000601@linbox.com> <42CAACA3.1050706@free.fr> <42DE14D7.8040101@linbox.com> <42DE1B29.3050205@stroeder.com> Message-ID: <42DE407F.9010409@linbox.com> Thanks, it works well. I'll try to create function to delete properly an objectClass, preserve same Attributes between schema. I can post the function... if you want to integrate it into Python-Ldap. It can be useful. Michael Str?der a ?crit : >J?r?me Wax wrote: > > >>Can I retrieve all required and sufficient attributes for a specific >>schema with Python-Ldap ? >> >> > >There's a undocumented module ldap.schema. See Demo/schema.py for a >couple of examples. But first you should understand all the nits and >bits about correct usage of LDAPv3 subschema subentries. > >Note: The API of ldap.schema might change in the future. I.e. I'm still >thinking about changing the ill-designed error handling for non-existent >schema elements. > >Ciao, Michael. > > > From michael at stroeder.com Wed Jul 20 14:45:36 2005 From: michael at stroeder.com (=?ISO-8859-1?Q?Michael_Str=F6der?=) Date: Wed, 20 Jul 2005 14:45:36 +0200 Subject: retrieves attributes from schema In-Reply-To: <42DE407F.9010409@linbox.com> References: <42CAA6F1.8050809@linbox.com> <42CAA874.2000603@free.fr> <42CAAA26.1000601@linbox.com> <42CAACA3.1050706@free.fr> <42DE14D7.8040101@linbox.com> <42DE1B29.3050205@stroeder.com> <42DE407F.9010409@linbox.com> Message-ID: <42DE4770.5050406@stroeder.com> J?r?me Wax wrote: > > I'll try to create function to delete properly an objectClass, preserve > same Attributes between schema. > I can post the function... if you want to integrate it into Python-Ldap. This could be a method of class ldap.schema.models.Entry. Please take a closer look at this. Ciao, Michael. From jerome.wax at linbox.com Wed Jul 20 15:26:09 2005 From: jerome.wax at linbox.com (=?ISO-8859-1?Q?J=E9r=F4me_Wax?=) Date: Wed, 20 Jul 2005 15:26:09 +0200 Subject: bugs in ldap.OBJECT_CLASS_VIOLATION ? Message-ID: <42DE50F1.6030309@linbox.com> I've got this error message for my function who delete objectClass on an entry In this example i delete objectClass "person" My function try to delete sn,telephoneNumber and seeAlso attributes... cause the over are used by other schema. I've got this error message ldap.OBJECT_CLASS_VIOLATION: {'info': "object class 'inetOrgPerson' requires attribute 'sn'", 'desc': 'Object class violation'} But sn is not a required attribute for inetOrgPerson... and inetOrgPerson schema response doesn't contain sn attribute... From michael at stroeder.com Wed Jul 20 17:10:57 2005 From: michael at stroeder.com (=?ISO-8859-1?Q?Michael_Str=F6der?=) Date: Wed, 20 Jul 2005 17:10:57 +0200 Subject: bugs in ldap.OBJECT_CLASS_VIOLATION ? In-Reply-To: <42DE50F1.6030309@linbox.com> References: <42DE50F1.6030309@linbox.com> Message-ID: <42DE6981.50506@stroeder.com> J?r?me Wax wrote: > > ldap.OBJECT_CLASS_VIOLATION: {'info': "object class 'inetOrgPerson' > requires attribute 'sn'", 'desc': 'Object class violation'} Yepp. > But sn is not a required attribute for inetOrgPerson... It is required since inetOrgPerson is SUP organizationalPerson which is SUP person. > and inetOrgPerson schema response doesn't contain sn attribute... You have to resolve object class inheritance. Fortunately you can use ready-to-use methods: ldap.schema.subentry.SubSchema.attribute_types() Or the convenience wrapper method: ldap.schema.models.Entry.attribute_types(). BTW: Attribute types are derived via SUP too... Additionally I'd recommend to use the schema browser in http://www.web2ldap.de to dig your local LDAP server's schema. :-) Ciao, Michael. From jerome.wax at linbox.com Wed Jul 20 17:37:51 2005 From: jerome.wax at linbox.com (=?ISO-8859-1?Q?J=E9r=F4me_Wax?=) Date: Wed, 20 Jul 2005 17:37:51 +0200 Subject: get or set OpenLDAPaci Message-ID: <42DE6FCF.4070002@linbox.com> I've got a problem (again). Then I create an openexchange account on an ldap account, I must set OpenLDAPaci. like this *if* *not* "OpenLDAPaci" *in* newattrs: newattrs["OpenLDAPaci"]='1#entry#grant;r,w,s,c;cn,initials,mail,title,ou,l,birthday,description,street,postalcode,st,c,oxtimezone,homephone,mobile,pager,facsimiletelephonenumber,telephonenumber,labeleduri,jpegphoto,loginDestination,sn,givenname,;r,s,c;[all]#self#"' mlist = ldap.modlist.modifyModlist(attrs, newattrs) self.l.modify_s(cn, mlist) attrs is the entire attributes list. newattrs is the modified list. When I create and delete... it works. But if I recreate OX attributes... OpenLDAPaci already exist... but don't appear in attributes list and cause this: ldap.INAPPROPRIATE_MATCHING: {'info': 'modify/add: OpenLDAPaci: no equality matching rule', 'desc': 'Inappropriate matching'} How can I get OpenLDAPaci attribute to prevent this error ? thanks in advance -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael at stroeder.com Wed Jul 20 17:59:59 2005 From: michael at stroeder.com (=?ISO-8859-1?Q?Michael_Str=F6der?=) Date: Wed, 20 Jul 2005 17:59:59 +0200 Subject: get or set OpenLDAPaci In-Reply-To: <42DE6FCF.4070002@linbox.com> References: <42DE6FCF.4070002@linbox.com> Message-ID: <42DE74FF.4000201@stroeder.com> J?r?me Wax wrote: > > Then I create an openexchange account on an ldap account, Just curious, what project are you working on? > mlist = ldap.modlist.modifyModlist(attrs, newattrs) > self.l.modify_s(cn, mlist) Can you please post repr(mlist)? > attrs is the entire attributes list. > newattrs is the modified list. These are dictionaries, not lists! > When I create and delete... it works. > > But if I recreate OX attributes... OpenLDAPaci already exist... but don't appear in attributes list and cause this: > > ldap.INAPPROPRIATE_MATCHING: {'info': 'modify/add: OpenLDAPaci: no equality matching rule', 'desc': 'Inappropriate matching'} > > How can I get OpenLDAPaci attribute to prevent this error ? Probably you have to use ldap.MOD_REPLACE in mlist for attribute OpenLDAPaci instead of ldap.MOD_DELETE. Not sure if usage of ldap.modlist.modifyModlist() in every case. But first turn on python-ldap's debugging by setting trace_level=2 when calling ldap.initialize() and post the output. Example: l = ldap.initialize('ldap://localhost:1390',trace_level=2) Ciao, Michael. From jerome.wax at linbox.com Thu Jul 21 09:38:47 2005 From: jerome.wax at linbox.com (=?ISO-8859-1?Q?J=E9r=F4me_Wax?=) Date: Thu, 21 Jul 2005 09:38:47 +0200 Subject: get or set OpenLDAPaci In-Reply-To: <42DE74FF.4000201@stroeder.com> References: <42DE6FCF.4070002@linbox.com> <42DE74FF.4000201@stroeder.com> Message-ID: <42DF5107.8000302@linbox.com> Michael Str?der a ?crit : >J?r?me Wax wrote: > > >>Then I create an openexchange account on an ldap account, >> >> > >Just curious, what project are you working on? > > > > >>mlist = ldap.modlist.modifyModlist(attrs, newattrs) >>self.l.modify_s(cn, mlist) >> >> > >Can you please post repr(mlist)? > > [(0, 'mailDomain', 'linbox.com'), (1, 'objectClass', None), (0, 'objectClass', ['inetOrgPerson', 'posixAccount', 'shadowAccount', 'top', 'person', 'sambaSamAccount', 'OXUserObject']), (0, 'OXTimeZone', 'Europe/Paris'), (0, 'OXTaskDays', '5'), (0, 'OpenLDAPaci', '1#entry#grant;r,w,s,c;cn,initials,mail,title,ou,l,birthday,description,street,postalcode,st,c,oxtimezone,homephone,mobile,pager,facsimiletelephonenumber,telephonenumber,labeleduri,jpegphoto,loginDestination,sn,givenname,;r,s,c;[all]#self#"'), (1, 'preferredLanguage', None), (0, 'preferredLanguage', 'EN'), (0, 'OXGroupID', '500'), (1, 'mail', None), (0, 'mail', 'vincent at linbox.com'), (0, 'lnetMailAccess', '5'), (0, 'OXAppointmentDays', '5'), (0, 'userCountry', 'Tuxworld'), (1, 'o', None), (0, 'o', 'linbox'), (1, 'givenName', None), (0, 'givenName', 'vincent'), (0, 'mailEnabled', 'TRUE')] but attrs fetch on ldap entry of this user contain {'shadowMin': ['-1'], 'cn': ['vincent'], 'objectClass': ['inetOrgPerson', 'posixAccount', 'shadowAccount', 'top', 'person', 'sambaSamAccount'], 'uidNumber': ['10021'], 'sambaAcctFlags': ['[U ]'], 'shadowMax': ['99999'], 'shadowLastChange': ['11192'], 'shadowExpire': ['-1'], 'sambaPwdCanChange': ['1121872460'], 'uid': ['vincent'], 'shadowFlag': ['134538308'], 'preferredLanguage': ['EN'], 'userPassword': ['{crypt}351Hd48lGvZKo'], 'sambaPwdMustChange': ['2147483647'], 'sambaLMPassword': ['4E6319FFC67D969DAAD3B435B51404EE'], 'postalCode': ['57950'], 'mail': ['vincent at coin.fr'], 'loginShell': ['/bin/false'], 'gidNumber': ['10018'], 'sambaPasswordHistory': ['0000000000000000000000000000000000000000000000000000000000000000'], 'sambaPwdLastSet': ['1121872460'], 'sambaPrimaryGroupSID': ['S-1-5-21-1297919630-73438211-3158585458-21037'], 'sambaNTPassword': ['90076DCEE4C9C5772477679A8CFE38AE'], 'displayName': ['franky vincent'], 'shadowWarning': ['7'], 'labeledURI': ['http://lo2k.net'], 'shadowInactive': ['-1'], 'l': ['Montigny les Metz'], 'o': ['linbox'], 'sambaSID': ['S-1-5-21-1297919630-73438211-3158585458-21042'], 'gecos': ['vincent franky'], 'sn': ['franky'], 'homeDirectory': ['/home/vincent'], 'givenName': ['vincent']} so no OpenLDAPaci key > > >> attrs is the entire attributes list. >>newattrs is the modified list. >> >> > >These are dictionaries, not lists! > > You have reason :) > > >>When I create and delete... it works. >> >>But if I recreate OX attributes... OpenLDAPaci already exist... but don't appear in attributes list and cause this: >> >>ldap.INAPPROPRIATE_MATCHING: {'info': 'modify/add: OpenLDAPaci: no equality matching rule', 'desc': 'Inappropriate matching'} >> >>How can I get OpenLDAPaci attribute to prevent this error ? >> >> > >Probably you have to use ldap.MOD_REPLACE in mlist for attribute >OpenLDAPaci instead of ldap.MOD_DELETE. Not sure if usage of >ldap.modlist.modifyModlist() in every case. > > I'm not following you... I don't want to delete... just add or replace. >But first turn on python-ldap's debugging by setting trace_level=2 when >calling ldap.initialize() and post the output. > >Example: >l = ldap.initialize('ldap://localhost:1390',trace_level=2) > > Just respond me that *** ldap://127.0.0.1 - SimpleLDAPObject.set_option ((17, 3),{}) From shishkin.alexey at gmail.com Mon Jul 25 07:34:50 2005 From: shishkin.alexey at gmail.com (shishkin.alexey) Date: Mon, 25 Jul 2005 11:34:50 +0600 Subject: build error on RHEL3 (ES) Message-ID: <42e47629.54030325.3e48.ffffb201@mx.gmail.com> Hi there! Please help me to solve following issue. I'm get error when building python-ldap: gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC -DLDAPMODULE_VERSION=2.0.8 -IModules -I/usr/local/include -I/usr/local/include/sasl -I/usr/include -I/usr/lib/include -I/usr/include/python2.2 -c Modules/ldapcontrol.c -o build/temp.linux-i686-2.2/ldapcontrol.o Modules/ldapcontrol.c:204: syntax error before string constant Modules/ldapcontrol.c:208: warning: data definition has no type or storage class Modules/ldapcontrol.c:265: syntax error before string constant Modules/ldapcontrol.c:268: warning: data definition has no type or storage class Modules/ldapcontrol.c:306: `encode_rfc2696__doc__' undeclared here (not in a function) Modules/ldapcontrol.c:306: initializer element is not constant Modules/ldapcontrol.c:306: (near initialization for `methods[0].ml_doc') Modules/ldapcontrol.c:306: initializer element is not constant Modules/ldapcontrol.c:306: (near initialization for `methods[0]') Modules/ldapcontrol.c:307: `decode_rfc2696__doc__' undeclared here (not in a function) Modules/ldapcontrol.c:307: initializer element is not constant Modules/ldapcontrol.c:307: (near initialization for `methods[1].ml_doc') Modules/ldapcontrol.c:307: initializer element is not constant Modules/ldapcontrol.c:307: (near initialization for `methods[1]') Modules/ldapcontrol.c:308: initializer element is not constant Modules/ldapcontrol.c:308: (near initialization for `methods[2]') error: command 'gcc' failed with exit status 1 Packets installed: python-2.2.3-5 python-ldap-2.0.8 openldap-2.3.4 ( configured --with-cyrus-sasl --with-tls ) cyrus-sasl-2.1.21 openssl-devel-0.9.7a-22.1 openssl096b-0.9.6b-16 openssl-0.9.7a-22.1 Here is my setup.cfg: # Example for setup.cfg # You have to edit this file to reflect your system configuation # $Id: setup.cfg.suse-linux,v 1.1 2003/08/20 10:04:34 stroeder Exp $ [_ldap] # Section for compiling the C extension module # for wrapping OpenLDAP 2 libs library_dirs = /usr/local/lib /usr/local/lib/sasl2 /usr/lib include_dirs = /usr/local/include /usr/local/include/sasl /usr/include /usr/lib/include extra_compile_args = extra_objects = # Example for full-featured SuSE build: # Support for StartTLS/LDAPS, SASL bind and reentrant libldap_r. # This needs recent OpenLDAP 2.0.26+ or 2.1.3+ built with # ./configure --with-cyrus-sasl --with-tls libs = ldap_r lber ssl crypto sasl2 [install] # Installation options compile = 1 optimize = 1 # For SuSE Linux 8.2 [bdist_rpm] provides = python-ldap requires = python openldap2-client openssl cyrus-sasl2 distribution_name = SuSE Linux 8.2 release = 1 packager = Michael Stroeder doc_files = CHANGES README INSTALL TODO Demo/ -- shishkin From Andreas.Ames at comergo.com Tue Jul 26 13:12:59 2005 From: Andreas.Ames at comergo.com (Ames Andreas) Date: Tue, 26 Jul 2005 13:12:59 +0200 Subject: build error on RHEL3 (ES) Message-ID: Hi, shishkin alexey wrote: > gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC > -DLDAPMODULE_VERSION=2.0.8 -IModules -I/usr/local/include > -I/usr/local/include/sasl -I/usr/include -I/usr/lib/include > -I/usr/include/python2.2 -c Modules/ldapcontrol.c -o > build/temp.linux-i686-2.2/ldapcontrol.o > Modules/ldapcontrol.c:204: syntax error before string constant [...] > Packets installed: > > python-2.2.3-5 I guess, this is the problem. I use the PyDoc_STRVAR macro which is apparently only available from python 2.3 and up (although I haven't checked, I know it is a relatively recent addition to python). Are you able to switch to a more recent version of python? Given that you seem to use sort of an "enterprise" linux, this is probably not an option. In this case you might try to replace the offending line by: static char encode_rfc2696__doc__[] = "encode_page_control(blabla)"; But please be aware that this is untested and that I'm not sure that this is my only 2.3ism. Please also note that PyDoc_STRVAR is used twice within the module. HTH, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com From michael at stroeder.com Tue Jul 26 13:43:41 2005 From: michael at stroeder.com (=?ISO-8859-1?Q?Michael_Str=F6der?=) Date: Tue, 26 Jul 2005 13:43:41 +0200 Subject: build error on RHEL3 (ES) In-Reply-To: References: Message-ID: <42E621ED.6030005@stroeder.com> Ames Andreas wrote: > > static char encode_rfc2696__doc__[] = "encode_page_control(blabla)"; Frankly I'd like to drop __doc__ strings in the C part completely. It's much better to define __doc__ strings for the class methods, in this case methods of class ldap.control.SimplePagedResultsControl. That's where programmers and tools like pydoc expect them to be. Ciao, Michael. From michael at stroeder.com Tue Jul 26 14:03:42 2005 From: michael at stroeder.com (=?ISO-8859-1?Q?Michael_Str=F6der?=) Date: Tue, 26 Jul 2005 14:03:42 +0200 Subject: build error on RHEL3 (ES) In-Reply-To: <42E621ED.6030005@stroeder.com> References: <42E621ED.6030005@stroeder.com> Message-ID: <42E6269E.1060003@stroeder.com> Michael Str?der wrote: > Ames Andreas wrote: > >>static char encode_rfc2696__doc__[] = "encode_page_control(blabla)"; > > Frankly I'd like to drop __doc__ strings in the C part completely. > > It's much better to define __doc__ strings for the class methods, in > this case methods of class ldap.control.SimplePagedResultsControl. > That's where programmers and tools like pydoc expect them to be. I've checked in a new version of ldapcontrol.c without the __doc__ strings. I'd like to keep the C part under Modules/ as lean as possible. Please test. Ciao, Michael. From shishkin.alexey at gmail.com Thu Jul 28 14:29:34 2005 From: shishkin.alexey at gmail.com (shishkin.alexey) Date: Thu, 28 Jul 2005 18:29:34 +0600 Subject: build error on RHEL3 (ES) In-Reply-To: <42E6269E.1060003@stroeder.com> Message-ID: <42e8cfeb.6d61f8ca.57f2.3d97@mx.gmail.com> Big thanks you all! I've checked up latest version of ldapcontrol.c from cvs and have successfully build python-ldap. -- shishkin -----Original Message----- From: python-ldap-dev-admin at lists.sourceforge.net [mailto:python-ldap-dev-admin at lists.sourceforge.net] On Behalf Of Michael Str?der Sent: Tuesday, July 26, 2005 6:04 PM To: python-ldap-dev at lists.sourceforge.net Subject: Re: build error on RHEL3 (ES) Michael Str?der wrote: > Ames Andreas wrote: > >>static char encode_rfc2696__doc__[] = "encode_page_control(blabla)"; > > Frankly I'd like to drop __doc__ strings in the C part completely. > > It's much better to define __doc__ strings for the class methods, in > this case methods of class ldap.control.SimplePagedResultsControl. > That's where programmers and tools like pydoc expect them to be. I've checked in a new version of ldapcontrol.c without the __doc__ strings. I'd like to keep the C part under Modules/ as lean as possible. Please test. Ciao, Michael. From michael at stroeder.com Wed Aug 24 11:55:32 2005 From: michael at stroeder.com (=?ISO-8859-1?Q?Michael_Str=F6der?=) Date: Wed, 24 Aug 2005 11:55:32 +0200 Subject: ldaputil In-Reply-To: <430B666A.80508@tonychachere.com> References: <430B666A.80508@tonychachere.com> Message-ID: <430C4414.2050201@stroeder.com> Eric G Ortego wrote: > I have been learning python and ldap lately and ran across the ldaputil > folder in web2ldap looking for password hashing python code. > My question is what is the latest version of the passwd.py util? Have > these password classes been tested & are they being used anywhere? They were developed for web2ldap. Generating the hashes work. Not sure whether the over-designed modify request code works though. Ciao, Michael. P.S.: Please don't e-mail me personally. I'd prefer to receive such support requests through python-ldap's mailing list (Cc:-ed). From michael at stroeder.com Tue Sep 20 14:12:25 2005 From: michael at stroeder.com (=?ISO-8859-1?Q?Michael_Str=F6der?=) Date: Tue, 20 Sep 2005 14:12:25 +0200 Subject: Error: Schema fetching on Oracle Directory Server In-Reply-To: <421F5737.4000507@stroeder.com> References: <127079e10501100613681c6f1a@mail.gmail.com> <41E2AAD0.4030206@stroeder.com> <127079e10501101622478946dc@mail.gmail.com> <41E4C8F1.7050907@stroeder.com> <41EF6A7A.3040808@stroeder.com> <127079e105012409222e525ebc@mail.gmail.com> <421F5737.4000507@stroeder.com> Message-ID: <432FFCA9.7080107@stroeder.com> Wido, Michael Str?der wrote: > Wido Depping wrote: > >> Attached are the updated testcase file and my improved split_tokens() >> function. > > Your patches were added to CVS. This new implementation of split_tokens() deletes the spaces from DESC schema attributes. I looked at the code and the main problem is right at the beginning of the function: tokenList = s.split(" ") >From my understanding there's no solution to save the spaces in DESC when using this code. I think there could be a better solution based on using keywordDict to find the relevant sections in the string. Still there would be some issues detecting whether the keyword appears inside colons. Ciao, Michael.