From: Chaos E. <cha...@gm...> - 2011-03-07 01:14:32
|
should we re-implement python-ldap on pyasn and get rid of depends on openldap libs? ---------- Forwarded message ---------- From: "Ilya Etingof" <il...@gl...> Date: Mar 7, 2011 12:18 AM Subject: [pyasn1-users] ANN: pyasn1-0.0.13a & pyasn1-modules-0.0.1a released To: <pya...@li...> This is to let you know that pyasn1-0.0.13a has been released. This new release brings the following major changes: * Very significant performance improvement on frequent operations * ASN.1 ANY type is fully supported * Enclosed documentation re-written and now covers many aspects * Minor bugfixes and improvements (see CHANGES) Another project news is that all ASN.1 protocol modules, previously distributed with pyasn1 as examples, were stripped off pyasn1 library and are now distributed alone. These modules were re-written to be importable and installable, thus easily used by other applications. The following protocol modules are now shipped with the pyasn1-modules package: * X.509 * PKCS#7 * OCSP * SNMP * SSH keys For each module a simple command-line tool is also included to help you test the them right away. -ilya ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ pyasn1-users mailing list pya...@li... https://lists.sourceforge.net/lists/listinfo/pyasn1-users |
From: Rich M. <ric...@gm...> - 2011-03-07 17:06:20
|
On 03/06/2011 06:14 PM, Chaos Eternal wrote: > > should we re-implement python-ldap on pyasn and get rid of depends on > openldap libs? > I vote no. Why would you want to do that? How would you implement TLS/SSL? How would you implement SASL/GSSAPI? How would you keep up with openldap client library development, which is the reference standard for LDAP in the FOSS world? > ---------- Forwarded message ---------- > From: "Ilya Etingof" <il...@gl... <mailto:il...@gl...>> > Date: Mar 7, 2011 12:18 AM > Subject: [pyasn1-users] ANN: pyasn1-0.0.13a & pyasn1-modules-0.0.1a > released > To: <pya...@li... > <mailto:pya...@li...>> > > > This is to let you know that pyasn1-0.0.13a has been released. This new > release brings the following major changes: > > * Very significant performance improvement on frequent operations > * ASN.1 ANY type is fully supported > * Enclosed documentation re-written and now covers many aspects > * Minor bugfixes and improvements (see CHANGES) > > Another project news is that all ASN.1 protocol modules, previously > distributed with pyasn1 as examples, were stripped off pyasn1 library and > are now distributed alone. > > These modules were re-written to be importable and installable, thus > easily used by other applications. > > The following protocol modules are now shipped with the pyasn1-modules > package: > > * X.509 > * PKCS#7 > * OCSP > * SNMP > * SSH keys > > For each module a simple command-line tool is also included to help you > test the them right away. > > -ilya > > ------------------------------------------------------------------------------ > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > _______________________________________________ > pyasn1-users mailing list > pya...@li... > <mailto:pya...@li...> > https://lists.sourceforge.net/lists/listinfo/pyasn1-users > > > ------------------------------------------------------------------------------ > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > > > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |
From: Rich M. <ric...@gm...> - 2011-03-07 17:53:58
|
On 03/07/2011 10:35 AM, Michael Ströder wrote: > Rich Megginson wrote: >> On 03/06/2011 06:14 PM, Chaos Eternal wrote: >>> should we re-implement python-ldap on pyasn and get rid of depends on >>> openldap libs? >>> >> I vote no. Why would you want to do that? How would you implement >> TLS/SSL? How would you implement SASL/GSSAPI? How would you keep up >> with openldap client library development, which is the reference >> standard for LDAP in the FOSS world? > David and me already thought about this two years ago. And for the same > reasons Rich mentioned I won't go that route because it's simply too much work > to get it right. Additionally there's the performance aspect. > > BTW: There is already a pure-Python LDAP module called 'ldaptor'. > http://eagain.net/talks/ldaptor/index.html > > But I'm currently using pyasn1 for certain LDAPv3 extended operations/controls > and therefore I am thinking about adding some of the basic LDAP-related ASN.1 > stuff to python-ldap 2.4.x. But this would introduce a dependency on pyasn1. > Pros/Cons? RHEL does not include pyasn1. But it is extremely useful for extops/controls - doing BER codec by hand is not fun. A mid-way approach would be to expose the liblber ber_scanf/ber_printf and support functions in python. If you do decide that it is necessary for python-ldap to use pyasn1, we can work on getting it into RHEL. The Fedora python-pyasn1 maintainer is one of the guys on the freeipa team which uses python-ldap heavily. > Ciao, Michael. |
From: Michael S. <mi...@st...> - 2011-03-07 18:19:49
|
Rich Megginson wrote: > RHEL does not include pyasn1. But it is extremely useful for > extops/controls - doing BER codec by hand is not fun. Yupp! > A mid-way > approach would be to expose the liblber ber_scanf/ber_printf and support > functions in python. Also an idea we already had. But I'm not a C programmer. So I'll stay away from that myself. But I will happily add a nice Python layer on top of your code. ;-} Make the C wrapper code as lean as possible. > If you do decide that it is necessary for python-ldap to use pyasn1, we > can work on getting it into RHEL. The Fedora python-pyasn1 maintainer > is one of the guys on the freeipa team which uses python-ldap heavily. Noted. Ciao, Michael. |
From: Rich M. <ric...@gm...> - 2011-03-07 18:34:01
|
On 03/07/2011 11:19 AM, Michael Ströder wrote: > Rich Megginson wrote: >> RHEL does not include pyasn1. But it is extremely useful for >> extops/controls - doing BER codec by hand is not fun. > Yupp! > >> A mid-way >> approach would be to expose the liblber ber_scanf/ber_printf and support >> functions in python. > Also an idea we already had. But I'm not a C programmer. So I'll stay away > from that myself. > > But I will happily add a nice Python layer on top of your code. ;-} > Make the C wrapper code as lean as possible. The biggest problem I see is how to pass in arguments to the varadic functions ber_scanf and ber_printf from python without completely rewriting those functions to accept an array of format specifiers and a corresponding array of values/pointers. It may be easier to just bite the bullet and add pyasn1 . . . >> If you do decide that it is necessary for python-ldap to use pyasn1, we >> can work on getting it into RHEL. The Fedora python-pyasn1 maintainer >> is one of the guys on the freeipa team which uses python-ldap heavily. > Noted. > > Ciao, Michael. |
From: Michael S. <mi...@st...> - 2011-03-07 17:35:34
|
Rich Megginson wrote: > On 03/06/2011 06:14 PM, Chaos Eternal wrote: >> >> should we re-implement python-ldap on pyasn and get rid of depends on >> openldap libs? >> > I vote no. Why would you want to do that? How would you implement > TLS/SSL? How would you implement SASL/GSSAPI? How would you keep up > with openldap client library development, which is the reference > standard for LDAP in the FOSS world? David and me already thought about this two years ago. And for the same reasons Rich mentioned I won't go that route because it's simply too much work to get it right. Additionally there's the performance aspect. BTW: There is already a pure-Python LDAP module called 'ldaptor'. http://eagain.net/talks/ldaptor/index.html But I'm currently using pyasn1 for certain LDAPv3 extended operations/controls and therefore I am thinking about adding some of the basic LDAP-related ASN.1 stuff to python-ldap 2.4.x. But this would introduce a dependency on pyasn1. Pros/Cons? Ciao, Michael. |