From encukou at gmail.com Fri Nov 26 10:41:44 2021 From: encukou at gmail.com (Petr Viktorin) Date: Fri, 26 Nov 2021 16:41:44 +0100 Subject: [python-ldap] ANN: python-ldap 3.4.0 Message-ID: <6e882ce6-8f89-c3b7-e5ea-5aac621fa057@gmail.com> You can find a new release of python-ldap here: https://pypi.python.org/pypi/python-ldap/3.4.0 See below for changes in this release. If you find any issues, please report them either on this mailing list or on the GitHub tracker: https://github.com/python-ldap/python-ldap/issues Git tag hash for the release: python-ldap-3.4.0 45af6845c1d2b9e9825b2f50176718f286f77a73 The tag is signed by my GPG key with fingerprint: 98FD 199F BEDE 218C 2218 CC0B C5A8 0F29 6195 7F02 -------- About the project: python-ldap provides an object-oriented API to access LDAP directory servers from Python programs. It mainly wraps the OpenLDAP 2.x libs for that purpose. Additionally it contains modules for other LDAP-related stuff (e.g. processing LDIF, LDAP URLs and LDAPv3 schema). Project's web site: https://www.python-ldap.org/ -------- Released 3.4.0 2021-11-26 This release requires Python 3.6 or above, and is tested with Python 3.6 to 3.10. Python 2 is no longer supported. New code in the python-ldap project is available under the MIT licence (available in ``LICENCE.MIT`` in the source). Several contributors have agreed to apply this licence their previous contributions as well. See the ``README`` for details. The following undocumented functions are deprecated and scheduled for removal: - ``ldap.cidict.strlist_intersection`` - ``ldap.cidict.strlist_minus`` - ``ldap.cidict.strlist_union`` Security fixes: * Fix inefficient regular expression which allows denial-of-service attacks when parsing specially-crafted LDAP schema. (GHSL-2021-117) Changes: * On MacOS, remove option to make LDAP connections from a file descriptor when built with the system libldap (which lacks the underlying function, ``ldap_init_fd``) * Attribute values of the post read control are now ``bytes`` instead of ISO8859-1 decoded ``str`` * ``LDAPUrl`` now treats urlscheme as case-insensitive * Several OpenLDAP options are now supported: * ``OPT_X_TLS_REQUIRE_SAN`` * ``OPT_X_SASL_SSF_EXTERNAL`` * ``OPT_X_TLS_PEERCERT`` Fixes: * The ``copy()`` method of ``cidict`` was added back. It was unintentionally removed in 3.3.0 * Fixed getting/setting ``SASL`` options on big endian platforms * Unknown LDAP result code are now converted to ``LDAPexception``, rather than raising a ``SystemError``. slapdtest: * Show stderr of slapd -Ttest * ``SlapdObject`` uses directory-based configuration of ``slapd`` * ``SlapdObject`` startup is now faster Infrastructure: * CI now runs on GitHub Actions rather than Travis CI. From encukou at gmail.com Fri Nov 26 11:02:39 2021 From: encukou at gmail.com (Petr Viktorin) Date: Fri, 26 Nov 2021 17:02:39 +0100 Subject: [python-ldap] Stepping down -- new maintainer wanted Message-ID: Hello, I no longer use python-ldap personally, or as part of my work, and I can't seem to find much time for the project. Although there are other reviewers, I feel I'm a bottleneck in getting contributions merged in and released. It is time for me to step down. If you contributed to the project and would like to take the role of primary maintainer, please let me know (on this list or privately). I'll pick someone and give them all the rights necessary to run the project (GitHub, PyPI, Pagure, Read the Docs). Also, the project is a bit short on active reviewers. If you contribute and would like the power to approve and merge contributions, let me know. I (or the new steward of the project) can get it sorted. Documentation for all roles is up at: https://www.python-ldap.org/en/latest/contributing.html As for the the python-ldap.org domain, it's a pain to transfer. I'm happy to keep under my name if the new maintainer(s) don't want to go through that. From encukou at gmail.com Mon Nov 29 05:22:49 2021 From: encukou at gmail.com (Petr Viktorin) Date: Mon, 29 Nov 2021 11:22:49 +0100 Subject: [python-ldap] New committers In-Reply-To: References: Message-ID: On 26. 11. 21 17:02, Petr Viktorin wrote: > Hello, > I no longer use python-ldap personally, or as part of my work, and I > can't seem to find much time for the project. Although there are other > reviewers, I feel I'm a bottleneck in getting contributions merged in > and released. > It is time for me to step down. > > If you contributed to the project and would like to take the role of > primary maintainer, please let me know (on this list or privately). I'll > pick someone and give them all the rights necessary to run the project > (GitHub, PyPI, Pagure, Read the Docs). > > Also, the project is a bit short on active reviewers. If you contribute > and would like the power to approve and merge contributions, let me > know. I (or the new steward of the project) can get it sorted. > > Documentation for all roles is up at: > https://www.python-ldap.org/en/latest/contributing.html Based on private correspondence I've given GitHub committer permissions to: - @Firstyear (William Brown) - @droideck (Simon Pichugin) - @mistotebe (Ond?ej Kuzn?k) (Send me Pagure usernames if you want access to our backup repo hosting too.) I've "rejected" one other person, who asked about the maintainer role and said they'd like to help. I've pointed them to PR reviews and issues instead. I'll wait a few more weeks before selecting a new primary maintainer and handing all the keys to them. From ondra at mistotebe.net Thu Dec 2 04:42:28 2021 From: ondra at mistotebe.net (=?utf-8?B?T25kxZllaiBLdXpuw61r?=) Date: Thu, 2 Dec 2021 10:42:28 +0100 Subject: [python-ldap] New committers In-Reply-To: References: Message-ID: <20211202094228.GO6219@mistotebe.net> On Mon, Nov 29, 2021 at 11:22:49AM +0100, Petr Viktorin wrote: > I'll wait a few more weeks before selecting a new primary maintainer and > handing all the keys to them. Having been around for a while and depending on python-ldap for quite a few of my tools, I would like to offer to become a (co-?)maintainer. Eventually, my aim would be to evolve my wrappers to provide a new API *alongside* the current one that is request based and asyncio aware. Thanks, -- Ond?ej Kuzn?k Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP From william at blackhats.net.au Thu Dec 2 15:40:20 2021 From: william at blackhats.net.au (William Brown) Date: Fri, 3 Dec 2021 06:40:20 +1000 Subject: [python-ldap] New committers In-Reply-To: <20211202094228.GO6219@mistotebe.net> References: <20211202094228.GO6219@mistotebe.net> Message-ID: <1DB2D777-A8D6-4050-A202-2A023737324C@blackhats.net.au> I'd vouch for Ondrej here, I've met him a few times at ldapcon/sambaxp and he's a good guy. -- Sincerely William > On 2 Dec 2021, at 20:58, Ond?ej Kuzn?k wrote: > > ?On Mon, Nov 29, 2021 at 11:22:49AM +0100, Petr Viktorin wrote: >> I'll wait a few more weeks before selecting a new primary maintainer and >> handing all the keys to them. > > Having been around for a while and depending on python-ldap for quite a > few of my tools, I would like to offer to become a (co-?)maintainer. > > Eventually, my aim would be to evolve my wrappers to provide a new API > *alongside* the current one that is request based and asyncio aware. > > Thanks, > > -- > Ond?ej Kuzn?k > Senior Software Engineer > Symas Corporation http://www.symas.com > Packaged, certified, and supported LDAP solutions powered by OpenLDAP > _______________________________________________ > python-ldap mailing list > python-ldap at python.org > https://mail.python.org/mailman/listinfo/python-ldap From spichugi at redhat.com Mon Dec 13 11:48:35 2021 From: spichugi at redhat.com (Simon Pichugin) Date: Mon, 13 Dec 2021 08:48:35 -0800 Subject: [python-ldap] Stepping down -- new maintainer wanted In-Reply-To: References: Message-ID: Hi folks! I'll be happy to become (co)maintainer. I work in the 389 DS team that actively uses python-ldap, tests and improves its functionality. Also, I maintain OpenLDAP on Fedora and RHEL and, presumably, I'll be the person behind python-ldap's RPM packages. So my main goal will be to keep everything working naturally, and I'll be very careful with introducing new features (still, I'll look into those, of course). I plan to improve the python-ldap's PR CI to work with containers and 389 DS, as it really tests most of the python-ldap's features in its codebase. Sincerely, Simon On Fri, Nov 26, 2021 at 8:02 AM Petr Viktorin wrote: > Hello, > I no longer use python-ldap personally, or as part of my work, and I > can't seem to find much time for the project. Although there are other > reviewers, I feel I'm a bottleneck in getting contributions merged in > and released. > It is time for me to step down. > > If you contributed to the project and would like to take the role of > primary maintainer, please let me know (on this list or privately). I'll > pick someone and give them all the rights necessary to run the project > (GitHub, PyPI, Pagure, Read the Docs). > > Also, the project is a bit short on active reviewers. If you contribute > and would like the power to approve and merge contributions, let me > know. I (or the new steward of the project) can get it sorted. > > Documentation for all roles is up at: > https://www.python-ldap.org/en/latest/contributing.html > > > As for the the python-ldap.org domain, it's a pain to transfer. I'm > happy to keep under my name if the new maintainer(s) don't want to go > through that. > _______________________________________________ > python-ldap mailing list > python-ldap at python.org > https://mail.python.org/mailman/listinfo/python-ldap > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at folino.us Tue Dec 14 21:48:21 2021 From: nick at folino.us (Nick Folino) Date: Tue, 14 Dec 2021 21:48:21 -0500 Subject: [python-ldap] ldap.REFERRAL exception only returns first referral Message-ID: I'm trying to catch and process referrals with python-ldap-3.4.0. I only see the first referral in the exception. Wireshark shows the entire list being returned from the consumer. Is this by design? Or is there a way to get the entire list from the exception? Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at folino.us Thu Dec 16 20:51:04 2021 From: nick at folino.us (Nick Folino) Date: Thu, 16 Dec 2021 20:51:04 -0500 Subject: [python-ldap] ldap.REFERRAL exception only returns first referral In-Reply-To: References: Message-ID: I found the code that passes the first referral only (Modules/constants.c). Was this done for a specific reason? Are there any developers still on the project that are familiar with that code? I don't mind helping to maintain this project, but it'll take me a while to get up to speed on the code. Nick On Tue, Dec 14, 2021 at 9:48 PM Nick Folino wrote: > I'm trying to catch and process referrals with python-ldap-3.4.0. > I only see the first referral in the exception. Wireshark shows the > entire list being returned from the consumer. > > Is this by design? Or is there a way to get the entire list from > the exception? > > Nick > -------------- next part -------------- An HTML attachment was scrubbed... URL: