Git in Postgres https://nesbitt.io/2026/02/26/git-in-postgres.html
It's interesting to me because it could probably be done more efficiently in #OpenLDAP. And there was a lot of work done to store git refs in #LMDB several years back, which ultimately never got merged. Using OpenLDAP also makes more sense for the federation usecase, since it has native replication, which is still a separate bolton for postgres.
#OpenLDAP 2.6.13 release candidate #1 available for testing https://lists.openldap.org/hyperkitty/list/openldap-technical@openldap.org/message/7PYPTFFD6TYTEG2XZLKPV4DJK5SJ2X2G/
On a même le droit à une petite chanson par @clementoudot pour parler d'IAM, OpenLDAP et AD à @alposs
RE: https://mastodon.social/@elementary/116076106987010771
Meanwhile, if you submit LLM-generated code to the #OpenLDAP Project, first I will berate you. *Then* I'll close it.
Machine generated #OpenLDAP bug reports - How it started / How it's going
I see the nano project finally wised up and is going to adopt the table the same table scheme #OpenLDAP and #Monero use with #LMDB https://xcancel.com/patrickluberus/status/2020380249952030768
@amirbkhan @_elena If you stop using billionaire software, just you, you are depriving them of your revenue, attention, and data. Each of us getting off "platforms" (Window, Mac, Facebook, X, etc.) is a member of the "walk away" revolt. And the continuing work to make Free and Open Source Software more accessible to the rest of them takes power away from the oligarchs AND the government they own. We are #OpenLDAP and #GCC #COBOL, two links in the chain.#
Dear bug hunters / fuzz testers: a one-shot command line tool is not a service. As such, feeding an invalid input to such a tool does not trigger a "denial of service". It simply causes a program to exit, that was already going to exit anyway. Categorizing such error-triggered exits as DoS is incorrect and any bug reports you submit to the #OpenLDAP Project categorized as such will be immediately closed as Invalid.
Stop wasting our time, thanks.
#OpenLDAP 2.6.11 release candidate available for testing
Private equity still trying to buy #OpenLDAP. If this was a real offer, clearly the buyers haven't done any due diligence, otherwise they'd know the OpenLDAP Project can't be sold.
No single person owns the intellectual property rights to the project, and there's no way to contact 100% of the rights owners.
PS: if a "free" software project requires you to sign your rights over to them before contributing, They're Doing It Wrong.
Private equity firms inquiring to purchase the #OpenLDAP Project. LOL...
@Gina The European Commission is already using Open Source Software (OpenLDAP) for its Directory Services. That's an Open Source foundation for your build-out. #ldap #openldap #opensource
Wer als Admin schon mal Nutzer, Gruppen und Zugriffsrechte verwalten musste, kennt das Chaos aus vielen Einzeltools. #OpenLDAP räumt hier auf und zentralisiert alles sauber an einem Ort. Deshalb ist der #Verzeichnisdienst ein Open-Source-Projekt ganz nach dem Geschmack unseres Admins Till Grünhagen.
Wer übrigens noch mehr über openLDAP lernen möchte, ist in unserer Akademie-Schulung für Fortgeschrittene bei openLDAP-Profi Stefan Kania genau richtig.
👉 https://www.heinlein-support.de/schulung/open-ldap-advanced
#Openldap is a powerful beast... https://github.com/h2o-commits/docker-openldap-replication
Deuxième édition du Worteks Identity Club — succès au rendez‑vous !
Merci à tous nos utilisateurs qui sont venus partager leurs IDs ! Spécialement aux 4 intervenants pour leur retour d'expérience sur l'implémentation de @lemonldapng @ltb_project ou @lsc_project .
Retrouvez les supports des présentations dans notre section conférences: https://www.worteks.com/opensource/conferences/2025-2-worteks-identity-club-2/
#OpenSource #Identity #LemonLDAP #Passwordless #LDAP #SSO #OpenLDAP @clementoudot @dcoutadeur @elecharny
EDIT: Solution is below!
So... I need to pick everyone's brains.
Trying to configure #LDAP #OpenLDAP on a #RedHat #RHEL server, and any and all attempts to use #ldapsearch to test the connection fail. The error is that it's 'unable to get local issuer certificate'.
So, yeah, it's an #SSL / #TLS error.
Here's where it gets weird.
When I use the TLS_CACERT environment variable to point to the root cert, same error. When I add the root cert to /etc/pki/ca-trust/source/anchors and run update-ca-trust, same error. Even when I check that it's been extracted properly, it's there in the extracted/pem directory.
I've tried adding all the intermediate certificates to the TLS_CACERT .pem file, and to the anchors directory, same error. Double-checked the validity dates, made sure the subject and issuer lines all matched up...
Tried testing the SSL/TLS certificates with 'openssl s_client -connect' and it connects reliably. Using the -verify_depth parameter to set the number to less than the number of certificates causes a failure, increasing it shows it's validated.
I can't use #curl, the version I've got is buggy for ldaps:// connections.
Any insight would be greatly appreciated before I lose my mind... :)
So, it turns out that OpenLDAP environment variables are prefixed with “LDAP” so it’s LDAPTLS_CACERT and LDAPTLS_REQCERT that modifies the behaviour, not the config parameters. This feels like bad form.
Ayé c'est fini le @worteks_com identité club 2. C'était chouette. Rendez-vous pour le prochain ? Merci @clementoudot et toute l'équipe.
#iam #openldap #lemonldapng #lsc #ltb
Heureux d'être au @worteks_com Identity Club 2. L'occasion d'échanger et de partager des retours d'expérience autour de l'IAM.
#IAM #LemonLDAPNG #OpenLDAP #LTB
