You can subscribe to this list here.
2000 |
Jan
|
Feb
(34) |
Mar
(9) |
Apr
|
May
(2) |
Jun
(14) |
Jul
(67) |
Aug
(34) |
Sep
(5) |
Oct
(20) |
Nov
(22) |
Dec
(31) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(15) |
Feb
(16) |
Mar
(20) |
Apr
(13) |
May
(72) |
Jun
(42) |
Jul
(41) |
Aug
(11) |
Sep
(19) |
Oct
(67) |
Nov
(59) |
Dec
(57) |
2002 |
Jan
(74) |
Feb
(69) |
Mar
(34) |
Apr
(55) |
May
(47) |
Jun
(74) |
Jul
(116) |
Aug
(68) |
Sep
(25) |
Oct
(42) |
Nov
(28) |
Dec
(52) |
2003 |
Jan
(19) |
Feb
(18) |
Mar
(35) |
Apr
(49) |
May
(73) |
Jun
(39) |
Jul
(26) |
Aug
(59) |
Sep
(33) |
Oct
(56) |
Nov
(69) |
Dec
(137) |
2004 |
Jan
(276) |
Feb
(15) |
Mar
(18) |
Apr
(27) |
May
(25) |
Jun
(7) |
Jul
(13) |
Aug
(2) |
Sep
(2) |
Oct
(10) |
Nov
(27) |
Dec
(28) |
2005 |
Jan
(22) |
Feb
(25) |
Mar
(41) |
Apr
(17) |
May
(36) |
Jun
(13) |
Jul
(22) |
Aug
(12) |
Sep
(23) |
Oct
(6) |
Nov
(4) |
Dec
|
2006 |
Jan
(11) |
Feb
(3) |
Mar
(5) |
Apr
(22) |
May
(1) |
Jun
(10) |
Jul
(19) |
Aug
(7) |
Sep
(25) |
Oct
(23) |
Nov
(5) |
Dec
(27) |
2007 |
Jan
(25) |
Feb
(17) |
Mar
(44) |
Apr
(8) |
May
(33) |
Jun
(31) |
Jul
(42) |
Aug
(16) |
Sep
(12) |
Oct
(16) |
Nov
(23) |
Dec
(73) |
2008 |
Jan
(26) |
Feb
(6) |
Mar
(46) |
Apr
(17) |
May
(1) |
Jun
(44) |
Jul
(9) |
Aug
(34) |
Sep
(20) |
Oct
(2) |
Nov
(4) |
Dec
(16) |
2009 |
Jan
(14) |
Feb
(3) |
Mar
(45) |
Apr
(52) |
May
(34) |
Jun
(32) |
Jul
(24) |
Aug
(52) |
Sep
(22) |
Oct
(23) |
Nov
(19) |
Dec
(10) |
2010 |
Jan
(10) |
Feb
(13) |
Mar
(22) |
Apr
(9) |
May
(1) |
Jun
(1) |
Jul
(8) |
Aug
(9) |
Sep
(10) |
Oct
(1) |
Nov
(2) |
Dec
(3) |
2011 |
Jan
|
Feb
(18) |
Mar
(39) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <MAI...@gr...> - 2004-01-20 10:43:50
|
This is the machine generated message from mail service. Unfortunately, we were not able to deliver your message to the following address(es): Это сообщение создано автоматически mail-сервисом. К сожалению, невозможно доставить сообщение по следующему адресу: <ie...@bk...>: 194.67.23.20 failed after I sent the message. Remote host said: 550 spam message discarded --- Below the next line is a header of the message. --- Ниже этой линии находится заголовок сообщения. Return-Path: <pyt...@li...> Received: (qmail 23995 invoked by alias); 20 Jan 2004 10:43:33 -0000 Delivered-To: ie...@nm... Received: (qmail 23804 invoked from network); 20 Jan 2004 10:43:31 -0000 Received: from mailr-2.tiscali.it (212.123.84.82) by grif.newmail.ru with SMTP; 20 Jan 2004 10:43:31 -0000 Received: from ppp-82-84-35-58.cust-adsl.tiscali.it (82.84.35.58) by mailr-2.tiscali.it with SMTP; 20 Jan 2004 11:42:31 +0100 Message-ID: <003801c3dfa4$dbcaddc9$58794aac@swymed> Reply-To: "=?windows-1251?B?w/Dz5/fo6ug=?=" <sc...@ho...> From: "=?windows-1251?B?w/Dz5/fo6ug=?=" <pyt...@li...> To: <ie...@ne...>, <ie...@re...>, <ie...@ci...>, <ie...@ma...>, <ie...@ah...>, <ie...@it...>, <ie...@it....>, <ie...@vz...>, <ie...@on...>, <ie...@da...>, <ie...@ie...>, <ie...@go...>, <ie...@on...>, <ie...@ms...>, <ie...@ms...>, <ief...@ge...>, <ief...@eu...>, <ie...@ho...>, <ieg...@mt...>, <ie...@fr...>, <ieg...@ya...>, <ieg...@ic...>, <ie...@nc...>, <ie...@zm...>, <ie...@on...>, <ie...@ii...>, <ie...@ze...>, <ie...@st...>, <ie...@ar...>, <ie...@pi...>, <ie...@la...>, <ie...@ca...>, <ie...@on...>, <ie...@ci...>, <ie...@ku...>, <ie...@tn...>, <ie...@ku...>, <ie...@ar...>, <ieo...@ap...>, <ie...@mt...>, <iep...@ri...>, <iep...@ri...ia.>, <iep...@ri...>, <iepo@astu. Subject: =?windows-1251?B?wfDo4+Dk4CDv8O705fHx6O7t4Ov87fv1IOPw8+f36Oru4iDv7uzu5uXyIO7x8/nl8fLi6PL8Og==?= Date: Tue, 20 Jan 2004 13:38:20 +0300 Organization: =?windows-1251?B?w/Dz5/fo6ug=?= MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1081 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1081 |
From: Mail D. S. <MAI...@ma...> - 2004-01-20 10:43:45
|
The following message to <ie...@nc...> was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 553-'5.3.0 REJECT spammer tiscali.it 212.123.84.81' |
From: Mail D. S. <MAI...@ma...> - 2004-01-20 10:43:36
|
The following message to <iep...@ri...ia.> was undeliverable. The reason for the problem: 5.1.2 - Bad destination host 'DNS Malformed Query Error looking up riga.mail.telia. (MX).' |
From: <mi...@st...> - 2004-01-20 10:40:12
|
Chris wrote: > I'm upgrading from OpenLDAP 2.1.22 to 2.2.4. Unfortunately, when I > rebuilt python-ldap I got a compile error in Modules/errors.c because > the definition of NUM_LDAP_ERRORS was negative, as it turns out the > ldap.h from 2.2.4 defines the API errors as negative numbers now, so the > problem here is obvious, Modules/errors.c reads: Thanks for catching this. Please bring your CVS working dir in sync and test. Ciao, Michael. |
From: Marc C. <mar...@ya...> - 2004-01-19 14:40:05
|
Thanks, Marc ===== ......\|||/................................................ (. .) -oOOo---0---oOOo------- |mar...@ya...| | ooO Ooo | ----( )--( )----------- () () __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: Marc C. <mar...@ya...> - 2004-01-19 13:17:21
|
unsubscribe ===== ......\|||/................................................ (. .) -oOOo---0---oOOo------- |mar...@ya...| | ooO Ooo | ----( )--( )----------- () () __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: <mi...@st...> - 2004-01-16 23:06:14
|
Roach, Mark R. wrote: > > File "/tmp/python-ldap-1.9.999.pre04/debian/tmp/usr/lib/python2.1/site-packages/ldap/__init__.py", line 31, in _ldap_call > ldap.OPERATIONS_ERROR: {'desc': 'Operations error', 'info': '00000000: LdapErr: DSID-0C0905FF, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece'} Seems you're using an outdated Debian package. This version had some issues. Please try whether the current version solves your problem. Also it's of interest which version of the OpenLDAP libs python-ldap is using on your system. Please upgrade to latest OpenLDAP 2.1.x especially if still OpenLDAP 2.0.x is around. Ciao, Michael. |
From: Roach, M. R. <mr...@ci...> - 2004-01-16 22:55:20
|
I am having trouble searching an exchange 2003 ldap server. I can use ldapsearch just fine against exchange, but python-ldap gives me a strange error: Here is an example of what I get. Does anyone have any suggestions? >>> l = ldap.open('10.13.1.11', 389) >>> l.protocol_version = 3 >>> l.simple_bind_s('ser...@ci...', 'password') >>> l.search_s('dc=cimplify, dc=net', ldap.SCOPE_SUBTREE, 'mail=mr...@ci...', ['cn']) Traceback (most recent call last): File "<stdin>", line 1, in ? File "/tmp/python-ldap-1.9.999.pre04/debian/tmp/usr/lib/python2.1/site-packages/ldap/ldapobject.py", line 410, in search_s File "/tmp/python-ldap-1.9.999.pre04/debian/tmp/usr/lib/python2.1/site-packages/ldap/ldapobject.py", line 414, in search_st File "/tmp/python-ldap-1.9.999.pre04/debian/tmp/usr/lib/python2.1/site-packages/ldap/ldapobject.py", line 355, in result File "/tmp/python-ldap-1.9.999.pre04/debian/tmp/usr/lib/python2.1/site-packages/ldap/ldapobject.py", line 59, in _ldap_call File "/tmp/python-ldap-1.9.999.pre04/debian/tmp/usr/lib/python2.1/site-packages/ldap/__init__.py", line 31, in _ldap_call ldap.OPERATIONS_ERROR: {'desc': 'Operations error', 'info': '00000000: LdapErr: DSID-0C0905FF, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece'} I know that the parameters are correct: as I say, the following works fine: ldapsearch -h 10.13.1.15 -x -W -D "ser...@ci..." \ -b dc=cimplify,dc=net "mail=mr...@ci..." Thanks for any suggestions you can offer. -Mark Roach |
From: Chris <py...@so...> - 2004-01-15 20:44:26
|
I'm upgrading from OpenLDAP 2.1.22 to 2.2.4. Unfortunately, when I rebuilt python-ldap I got a compile error in Modules/errors.c because the definition of NUM_LDAP_ERRORS was negative, as it turns out the ldap.h from 2.2.4 defines the API errors as negative numbers now, so the problem here is obvious, Modules/errors.c reads: #define NUM_LDAP_ERRORS LDAP_REFERRAL_LIMIT_EXCEEDED+1 static PyObject* errobjects[ NUM_LDAP_ERRORS ]; When on my system ldap.h defines LDAP_REFERRAL_LIMIT_EXCEEDED as -17. So I changed this to a positive number hoping my problem would be solved, and my scripts just seg fault when an error is being returned. Further looking into Modules/errors.c indicates to me that everything should be fine so long as the array size I choose for errobjects is large enough to accomodate all the error values it's populated with, but even with a large enough value I get seg faults. Any help would be greatly appreciated. Thanks in advance, Chris D. |
From: Jens V. <je...@zo...> - 2004-01-13 20:47:19
|
> I gave up for the moment on getting ldaps working on win32 and moved to > solaris with some success. Thought I would share some code for > resetting > passwords in Active Directory (which isnt as straight forward as it > seems). Does that really surprise you? > I had initially tried to use ldap.modlist to make the modlist, > but it kept trying to do an add, when you need to do a replace in the > case where you bind as administrator (which I am). > > # assumptions: > # a) its active directory > # b) you've bound to the ssl port > # c) you've bound as administrator > # d) your connection is called ldap_handle > account_dn = "cn=adam,ou=test,dc=ads" > password = "foo" > password_attr = "unicodePwd" > unicode_step1 = unicode("\"" + password + "\"", "iso-8859-1") > unicode_step2 = unicode_step1.encode("utf-16-le") > password_value = unicode_step2 > mods = [(ldap.MOD_REPLACE, password_attr, [password_value])] > ldap_handle.modify(account_dn, mods) > > Thought it might be handy to have this able to be found by the mailing > list search. Yeah, that's quite handy. For those people who are forced to use AD ;) jens |
From: Goucher, A. <ada...@hp...> - 2004-01-13 15:46:42
|
I gave up for the moment on getting ldaps working on win32 and moved to solaris with some success. Thought I would share some code for resetting passwords in Active Directory (which isnt as straight forward as it seems). I had initially tried to use ldap.modlist to make the modlist, but it kept trying to do an add, when you need to do a replace in the case where you bind as administrator (which I am). # assumptions: # a) its active directory # b) you've bound to the ssl port # c) you've bound as administrator # d) your connection is called ldap_handle account_dn =3D "cn=3Dadam,ou=3Dtest,dc=3Dads" password =3D "foo" password_attr =3D "unicodePwd" unicode_step1 =3D unicode("\"" + password + "\"", "iso-8859-1") unicode_step2 =3D unicode_step1.encode("utf-16-le") password_value =3D unicode_step2 mods =3D [(ldap.MOD_REPLACE, password_attr, [password_value])] ldap_handle.modify(account_dn, mods) Thought it might be handy to have this able to be found by the mailing list search. ______________________________ Adam Goucher Testing Group HP OpenView Select Access Hewlett-Packard 901 King St W. Toronto, Ontario M5V 3H5 Phone: +1-416-309-5208 Fax: +1-416-309-4406=20 |
From: <mi...@st...> - 2004-01-05 22:32:16
|
Goucher, Adam wrote: > > ldap.LDAPError: {'errnum': -1} Hmm, I'm clueless here. Might be the Win32 binary of python-ldap. Sorry, can't say anything about that. Ciao, Michael. |
From: Goucher, A. <ada...@hp...> - 2004-01-05 22:02:30
|
> Just guessing since you did not mention what "is hanging"=20 > means and you did=20 > not provide a Python traceback: You have to tell where to=20 > find the CA's=20 > certificate by calling >=20 > ldap.set_option(ldap.OPT_X_TLS_CACERTFILE,path_to_cacert_file) or=20 > ldap.set_option(ldap.OPT_X_TLS_CACERTDIR,path_of_cacert_dir). Using openssl's s_client it shows that the connection is doing TLS 1.0. = Consequently, I tried to do exactly as is suggested and received the = following. Traceback (most recent call last): File "c:\temp\ads.py", line 3, in ? ldap.set_option(ldap.OPT_X_TLS_CACERTFILE, "c:\temp\unicert.cer") File "C:\Python23\Lib\site-packages\ldap\functions.py", line 104, in = set_option _ldap_function_call(_ldap.set_option,option,invalue) File "C:\Python23\Lib\site-packages\ldap\__init__.py", line 62, in = _ldap_function_call result =3D apply(func,args,kwargs) ldap.LDAPError: {'errnum': -1} And the cert itself is pem encoded. -adam |
From: <mi...@st...> - 2004-01-05 21:43:06
|
Mauro Cicognini wrote: > > I'm at a loss here, but I know there are some TLS/SSL tools that will > allow you to kinda "debug" what's going on openssl s_client -connect ldap_host:6360 ... Ciao, Michael. |
From: Mauro C. <mci...@li...> - 2004-01-05 21:43:04
|
Michael Str=F6der wrote: > Please use "(objectclass=3D*)" since it could cause some strange effect= s=20 > with buggy LDAP servers. Second that! I had missed it, but definitely omitting the parentheses=20 does cause no end of problems. Still, if your script does work without encryption, I agree with Michael=20 that your problem probably rests in the SSL/TLS configuration. Mauro |
From: <mi...@st...> - 2004-01-05 21:38:58
|
Mauro Cicognini wrote: > Goucher, Adam wrote: > >> >> # search so we know we are connected >> p_search = p_handle.search("", ldap.SCOPE_BASE, "objectclass=*") >> > This call looks strange to me: iPlanet has always wanted a real base > there (i.e., no "" as you possibly could using Active Directory, but a > correct search base for your server like "dc=ldapserver, dc=acme, > dc=com" or similar). Since the search scope is base it would grab the server's Root DSE where you can read some configuration data, e.g. attribute'namingContexts'. This is almost a perfectly LDAPv3 compliant search request. Well, the filter string "objectclass=*" is *not* correct according to RFC2254. Please use "(objectclass=*)" since it could cause some strange effects with buggy LDAP servers. Side note: Make sure you use SunONE Directory Server 5.1SP2 or newer to avoid running into other strange bugs! But that's another story... ;-) Ciao, Michael. |
From: Mauro C. <mci...@li...> - 2004-01-05 21:31:31
|
Goucher, Adam wrote: >I have found that "" and an actual basename are two different items with >pretty much all directory servers I have used. Searching against "" will >return information about the server in general (such as the vendor and >version) whereas searching against a proper basename gives you site >specific information > > Aha. I'll try that. >Yes, I can login with different client to the ssl port. Is there a TLS >FAQ kicking around somewhere? I keep seeing it used interchangeably with >SSL but don't know anything about it. > TLS and SSL are in fact different beasts, TLS being a superset of SSL but different enough to warrant a name change. Certificates should work interchangeably, since most of the differences should be in how the peers negotiate crypto algorithms for the asymmetric and symmetric parts. However, it's tricky stuff and I wouldn't be surprised that communication is stalling because client & server can't find a common algorithm or a cert isn't "right" or something. I'm at a loss here, but I know there are some TLS/SSL tools that will allow you to kinda "debug" what's going on (I definitely saw a reference to one on the Netscape site). You could also try firing up a Linux box, install Python and Python-LDAP and see what happens (the Linux build is much more solid and widely tested). Mauro |
From: <mi...@st...> - 2004-01-05 21:31:17
|
Goucher, Adam wrote: > I'm trying to use python-ldap to connect to an iplanet 5.1 ldap. Which version of python-ldap and which version of the OpenLDAP libs are you using? > Connecting via ldap:// works, but the script is hanging when connecting > through ldaps://. Can anyone see what I am doing wrong? Just guessing since you did not mention what "is hanging" means and you did not provide a Python traceback: You have to tell where to find the CA's certificate by calling ldap.set_option(ldap.OPT_X_TLS_CACERTFILE,path_to_cacert_file) or ldap.set_option(ldap.OPT_X_TLS_CACERTDIR,path_of_cacert_dir). See Demo/initialize.py. > I am using python 2.3.2 for windows, and the python-ldap module found at > http://www.zope.org/Members/volkerw/LdapWin32.dsdfs Does this binary really have support for LDAP over SSL? Ciao, Michael. |
From: Goucher, A. <ada...@hp...> - 2004-01-05 19:05:42
|
> ># search so we know we are connected > >p_search =3D p_handle.search("", ldap.SCOPE_BASE, "objectclass=3D*") > > =20 > > > This call looks strange to me: iPlanet has always wanted a real base=20 > there (i.e., no "" as you possibly could using Active=20 > Directory, but a=20 > correct search base for your server like "dc=3Dldapserver, dc=3Dacme,=20 > dc=3Dcom" or similar). >=20 > If you say it does work using plain LDAP, however, this cannot be the=20 > reason for your script hanging, still I'm amazed it does, the RFC=20 > clearly states that you must explicitly set the search base=20 > and iPlanet=20 > have always prided themselves in being standards compliant (not like=20 > that other major software vendor ;-) I have found that "" and an actual basename are two different items with pretty much all directory servers I have used. Searching against "" will return information about the server in general (such as the vendor and version) whereas searching against a proper basename gives you site specific information =20 > I don't know this module, however you might want to give a try to my=20 > Win32 binary of Python-LDAP, you can find it at=20 > http://www.siosistemi.it/~mcicogni/ at the beginning of the=20 > page under=20 > "Python stuff". > Beware, your mileage may vary. Same problem, but a newer build, thanks. :) > If this doesn't work, either, it *might* be that your server isn't=20 > configured correctly (i.e., TLS Certificates and such): do=20 > other LDAPS=20 > client work? Yes, I can login with different client to the ssl port. Is there a TLS FAQ kicking around somewhere? I keep seeing it used interchangeably with SSL but don't know anything about it. -adam |
From: Mauro C. <mci...@li...> - 2004-01-05 18:52:12
|
Goucher, Adam wrote: >I'm trying to use python-ldap to connect to an iplanet 5.1 ldap. >Connecting via ldap:// works, but the script is hanging when connecting >through ldaps://. Can anyone see what I am doing wrong? > ><script> >import ldap >ldap.set_option(ldap.OPT_DEBUG_LEVEL, 5) > ># build our uri >uri = "ldaps://ldap_host:6360" > ># connect to the ldap server >p_handle = ldap.initialize(uri) >p_handle.protocol_version = ldap.VERSION3 > ># bind >p_handle.simple_bind("cn=directory manager", "*****") > ># search so we know we are connected >p_search = p_handle.search("", ldap.SCOPE_BASE, "objectclass=*") > > This call looks strange to me: iPlanet has always wanted a real base there (i.e., no "" as you possibly could using Active Directory, but a correct search base for your server like "dc=ldapserver, dc=acme, dc=com" or similar). If you say it does work using plain LDAP, however, this cannot be the reason for your script hanging, still I'm amazed it does, the RFC clearly states that you must explicitly set the search base and iPlanet have always prided themselves in being standards compliant (not like that other major software vendor ;-) >p_return = p_handle.result(p_search) >res_type, res_values = p_return >print res_values ></script> > ><output> >ldap_create >ldap_url_parse_ext(ldaps://ldap_host:6360) >ldap_bind >ldap_simple_bind >ldap_sasl_bind >ldap_send_initial_request >ldap_new_connection >ldap_int_open_connection >ldap_connect_to_host: TCP ldap_host:6360 >ldap_new_socket: 1904 >ldap_prepare_socket: 1904 >ldap_connect_to_host: Trying ldap_ip:6360 >ldap_connect_timeout: fd: 1904 tm: -1 async: 0 >ldap_ndelay_on: 1904 >ldap_ndelay_off: 1904 >ldap_open_defconn: successful >ldap_send_server_request >ldap_search_ext >put_filter: "objectclass=*" >put_filter: default >put_simple_filter: "objectclass=*" >ldap_send_initial_request >ldap_send_server_request >ldap_result msgid 2 >ldap_chkResponseList for msgid=2, all=1 >ldap_chkResponseList for msgid=2, all=1 >ldap_int_select ></ouput> > >I am using python 2.3.2 for windows, and the python-ldap module found at >http://www.zope.org/Members/volkerw/LdapWin32.dsdfs > > I don't know this module, however you might want to give a try to my Win32 binary of Python-LDAP, you can find it at http://www.siosistemi.it/~mcicogni/ at the beginning of the page under "Python stuff". Beware, your mileage may vary. If this doesn't work, either, it *might* be that your server isn't configured correctly (i.e., TLS Certificates and such): do other LDAPS client work? Mauro |
From: Goucher, A. <ada...@hp...> - 2004-01-05 18:25:39
|
6360 is the correct port for this server (we have multiple servers using various ports on that machine). -adam -----Original Message----- From: charlie derr [mailto:cd...@si...]=20 Sent: Monday, January 05, 2004 1:22 PM To: Goucher, Adam Cc: pyt...@li... Subject: Re: Hanging during ldaps My first guess would be to use port 636 instead of 6360 -- if that=20 doesn't work, I'd next try leaving the port specification off entirely=20 (start_tls should encrypt traffic on port 389 if the server is=20 configured correctly). good luck, ~c Goucher, Adam wrote: > I'm trying to use python-ldap to connect to an iplanet 5.1 ldap.=20 > Connecting via ldap:// works, but the script is hanging when=20 > connecting through ldaps://. Can anyone see what I am doing wrong? >=20 > <script> > import ldap > ldap.set_option(ldap.OPT_DEBUG_LEVEL, 5) >=20 > # build our uri > uri =3D "ldaps://ldap_host:6360" >=20 > # connect to the ldap server > p_handle =3D ldap.initialize(uri) > p_handle.protocol_version =3D ldap.VERSION3 >=20 > # bind > p_handle.simple_bind("cn=3Ddirectory manager", "*****") >=20 > # search so we know we are connected > p_search =3D p_handle.search("", ldap.SCOPE_BASE, "objectclass=3D*")=20 > p_return =3D p_handle.result(p_search) res_type, res_values =3D = p_return > print res_values > </script> >=20 > <output> > ldap_create > ldap_url_parse_ext(ldaps://ldap_host:6360) > ldap_bind > ldap_simple_bind > ldap_sasl_bind > ldap_send_initial_request > ldap_new_connection > ldap_int_open_connection > ldap_connect_to_host: TCP ldap_host:6360 > ldap_new_socket: 1904 > ldap_prepare_socket: 1904 > ldap_connect_to_host: Trying ldap_ip:6360 > ldap_connect_timeout: fd: 1904 tm: -1 async: 0 > ldap_ndelay_on: 1904 > ldap_ndelay_off: 1904 > ldap_open_defconn: successful > ldap_send_server_request > ldap_search_ext > put_filter: "objectclass=3D*" > put_filter: default > put_simple_filter: "objectclass=3D*" > ldap_send_initial_request > ldap_send_server_request > ldap_result msgid 2 > ldap_chkResponseList for msgid=3D2, all=3D1 > ldap_chkResponseList for msgid=3D2, all=3D1 > ldap_int_select > </ouput> >=20 > I am using python 2.3.2 for windows, and the python-ldap module found=20 > at http://www.zope.org/Members/volkerw/LdapWin32.dsdfs >=20 > ______________________________ > Adam Goucher > Testing Group > HP OpenView Select Access > Hewlett-Packard > 901 King St W. > Toronto, Ontario > M5V 3H5 >=20 > Phone: +1-416-309-5208 > Fax: +1-416-309-4406 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. Become an=20 > expert in LINUX or just sharpen your skills. Sign up for IBM's Free=20 > Linux Tutorials. Learn everything from the bash shell to sys admin.=20 > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dclick > _______________________________________________ > Python-LDAP-dev mailing list Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev >=20 |
From: charlie d. <cd...@si...> - 2004-01-05 18:22:14
|
My first guess would be to use port 636 instead of 6360 -- if that doesn't work, I'd next try leaving the port specification off entirely (start_tls should encrypt traffic on port 389 if the server is configured correctly). good luck, ~c Goucher, Adam wrote: > I'm trying to use python-ldap to connect to an iplanet 5.1 ldap. > Connecting via ldap:// works, but the script is hanging when connecting > through ldaps://. Can anyone see what I am doing wrong? > > <script> > import ldap > ldap.set_option(ldap.OPT_DEBUG_LEVEL, 5) > > # build our uri > uri = "ldaps://ldap_host:6360" > > # connect to the ldap server > p_handle = ldap.initialize(uri) > p_handle.protocol_version = ldap.VERSION3 > > # bind > p_handle.simple_bind("cn=directory manager", "*****") > > # search so we know we are connected > p_search = p_handle.search("", ldap.SCOPE_BASE, "objectclass=*") > p_return = p_handle.result(p_search) > res_type, res_values = p_return > print res_values > </script> > > <output> > ldap_create > ldap_url_parse_ext(ldaps://ldap_host:6360) > ldap_bind > ldap_simple_bind > ldap_sasl_bind > ldap_send_initial_request > ldap_new_connection > ldap_int_open_connection > ldap_connect_to_host: TCP ldap_host:6360 > ldap_new_socket: 1904 > ldap_prepare_socket: 1904 > ldap_connect_to_host: Trying ldap_ip:6360 > ldap_connect_timeout: fd: 1904 tm: -1 async: 0 > ldap_ndelay_on: 1904 > ldap_ndelay_off: 1904 > ldap_open_defconn: successful > ldap_send_server_request > ldap_search_ext > put_filter: "objectclass=*" > put_filter: default > put_simple_filter: "objectclass=*" > ldap_send_initial_request > ldap_send_server_request > ldap_result msgid 2 > ldap_chkResponseList for msgid=2, all=1 > ldap_chkResponseList for msgid=2, all=1 > ldap_int_select > </ouput> > > I am using python 2.3.2 for windows, and the python-ldap module found at > http://www.zope.org/Members/volkerw/LdapWin32.dsdfs > > ______________________________ > Adam Goucher > Testing Group > HP OpenView Select Access > Hewlett-Packard > 901 King St W. > Toronto, Ontario > M5V 3H5 > > Phone: +1-416-309-5208 > Fax: +1-416-309-4406 > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev > |
From: Goucher, A. <ada...@hp...> - 2004-01-05 18:07:35
|
I'm trying to use python-ldap to connect to an iplanet 5.1 ldap. Connecting via ldap:// works, but the script is hanging when connecting through ldaps://. Can anyone see what I am doing wrong? <script> import ldap ldap.set_option(ldap.OPT_DEBUG_LEVEL, 5) # build our uri uri =3D "ldaps://ldap_host:6360" # connect to the ldap server p_handle =3D ldap.initialize(uri) p_handle.protocol_version =3D ldap.VERSION3 # bind p_handle.simple_bind("cn=3Ddirectory manager", "*****") # search so we know we are connected p_search =3D p_handle.search("", ldap.SCOPE_BASE, "objectclass=3D*") p_return =3D p_handle.result(p_search) res_type, res_values =3D p_return print res_values </script> <output> ldap_create ldap_url_parse_ext(ldaps://ldap_host:6360) ldap_bind ldap_simple_bind ldap_sasl_bind ldap_send_initial_request ldap_new_connection ldap_int_open_connection ldap_connect_to_host: TCP ldap_host:6360 ldap_new_socket: 1904 ldap_prepare_socket: 1904 ldap_connect_to_host: Trying ldap_ip:6360 ldap_connect_timeout: fd: 1904 tm: -1 async: 0 ldap_ndelay_on: 1904 ldap_ndelay_off: 1904 ldap_open_defconn: successful ldap_send_server_request ldap_search_ext put_filter: "objectclass=3D*" put_filter: default put_simple_filter: "objectclass=3D*" ldap_send_initial_request ldap_send_server_request ldap_result msgid 2 ldap_chkResponseList for msgid=3D2, all=3D1 ldap_chkResponseList for msgid=3D2, all=3D1 ldap_int_select </ouput> I am using python 2.3.2 for windows, and the python-ldap module found at http://www.zope.org/Members/volkerw/LdapWin32.dsdfs=20 ______________________________ Adam Goucher Testing Group HP OpenView Select Access Hewlett-Packard 901 King St W. Toronto, Ontario M5V 3H5 Phone: +1-416-309-5208 Fax: +1-416-309-4406=20 |
From: Jens V. <je...@zo...> - 2003-12-23 12:58:00
|
>>> >> Building and some simple bind/search tests against the built-in >> OpenLDAP on Mac OS X 10.3.1 work fine. > > Unfortunately there is no new code in bind/search. ;-) > > One should test add(), modify(), delete(), compare(), unbind() or > their _s counterparts. OK, just used it in Zope with the LDAPUserFolder, now I can say that add_s, modify_s and delete_s work ;) jens |
From: <mi...@st...> - 2003-12-23 11:41:01
|
Jens Vagelpohl wrote: >> Please update your local CVS directory and test! > > Building and some simple bind/search tests against the built-in OpenLDAP > on Mac OS X 10.3.1 work fine. Unfortunately there is no new code in bind/search. ;-) One should test add(), modify(), delete(), compare(), unbind() or their _s counterparts. Ciao, Michael. |