News for hackers. Stuff that matters.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by zokier on Wednesday February 18, 2026 @08:18AM (#47060635)
I feel this is one of the weaknesses of Linux/unix ecosystem. The freeipa/sssd/nss/pam/krb/ldap/dns (+keycloak/samba/...) etc stack is just incredibly byzantine. I'm sure it is technically very capable in the right hands, but to me it feels like intractable mountain of things and worst of all the failure modes are pretty bad; you can accidentally leave security holes or alternatively lock yourself out.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by evanjrowley on Wednesday February 18, 2026 @10:31AM (#47062092)
Microsoft is pushing everyone onto Entra. There are so many exploits for AD but few for Entra.

Tenable has been pushing an internal initiative to eliminate all AD use. This action speaks volumes considering they acquired an AD security company and sell a product specifically designed to secure AD.

The consequences of a compromised AD domain are drastic. We should not try to build the same vulnerabilities into Linux environments, but it’s undeniable there is value in leveraging FreeIPA et al. to interoperate with legacy environments.

Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by elcritch on Thursday February 19, 2026 @12:30AM (#47070272)
The byzantine and overly complex nature of FreeIPA is a feature not a bug. It lends itself to consulting money for RedHat et al in those legacy markets. Sure, the server might be free but good luck getting it running.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by ipython on Wednesday February 18, 2026 @08:39AM (#47060803)
Yes. And Microsoft Active Directory has integrated this stack with an easy to use graphical interface for almost 30 years now.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by bzzzt on Wednesday February 18, 2026 @08:58AM (#47060957)
Active directory is dying along with local computer networks. Microsoft is pushing customers to Entra (formerly Azure Active directory). Modern, hybrid AD is not easy to use and difficult to manage.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by jabl on Wednesday February 18, 2026 @09:47AM (#47061510)
There's https://himmelblau-idm.org/ for a Linux client for Entra. Haven't tried it myself though.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by dijit on Wednesday February 18, 2026 @09:54AM (#47061596)
Doesn't FreeIPA work with EntraID? I used to use it with Exchange and it worked pretty well.. (or, as well as any non-microsoft product that has to intergrate with Microsoft products at least).
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by bzzzt on Wednesday February 18, 2026 @11:04AM (#47062489)
Looks nice, all it needs is an OSS server now ;)
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by dijit on Wednesday February 18, 2026 @09:53AM (#47061581)
This is 100% the current situation, and it's worth mentioning because clearly you have a finger on the pulse here - and that needs to be stated for others.

But, I wonder if Microsoft might reverse their stance on EntraID being SaaS; with the handwringing about sovreignty from Europe.

Back when "the deal" was made with Microsoft to basically embed itself into the digital ecosystem of every government, major institution and company in Europe: it was not the case that a member of the european parliament could have their mail disabled arbitrarily by Microsoft- such a thing was technically possible through a lot of hoops but it was significantly less feasible.

If Microsoft was to reverse course then I'm sure it would stop all the handwringing, even if people would continue to use the EntraID product in reality.

Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by bzzzt on Wednesday February 18, 2026 @11:01AM (#47062448)
I don't see Microsoft backing down from their SaaS push: it's necessary for authentication and authorization in all their Office 365 (or whatever it's called now) applications, also on platforms not running Microsoft clients. Beside that Entra is an OIDC server which makes it possible to integrate other SaaS applications in a domain which is near impossible to do if you only have local authentication.

Of course, you can still run local AD which synchronizes with Entra, but that means you get the worst of both worlds: you are paying for the cloud software but still have to manage your own servers.

Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by esseph on Wednesday February 18, 2026 @09:44AM (#47061470)
> dying along with local computer networks

I have seen the exact opposite, with people moving to things like jumpcloud, keycloak, authentik, etc.

Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by bzzzt on Wednesday February 18, 2026 @11:02AM (#47062464)
Those are all apps running in the cloud. I meant the classic Windows AD company LAN like solutions where the clients, server and network are tightly coupled.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by esseph on Wednesday February 18, 2026 @03:01PM (#47065574)
> Those are all apps running in the cloud.

Authentik and others can be deployed as docker containers that can be deployed any way you wish.

> I meant the classic Windows AD company LAN like solutions where the clients, server and network are tightly coupled.

In any mixed environment these days of Windows PCs, MacOS, and Linux, yeah, you can use a SaaS like jumpcloud with support for all of them, or you can integrate them into the ldap/kerb backend of your choice. Bonus points if your network devices are using RADIUS auth to the same identity source.

Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by amaccuish on Wednesday February 18, 2026 @10:13AM (#47061851)
Jumpcloud is SaaS.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by esseph on Wednesday February 18, 2026 @10:51AM (#47062296)
Yes, but it's not Microsoft Active Directory or Entra, which was my point.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by ElectricalUnion on Wednesday February 18, 2026 @08:59AM (#47060961)
Ideally you want to run all those trusted (read: security critical, if compromised entire system is no longer trustworthy) processes on separated and audited machines, but instead busy people end up running them all together because they happen to be packaged together (like FreeIPA or Active Directory), and that makes it even harder to secure them correctly.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by tremon on Wednesday February 18, 2026 @09:29AM (#47061290)
There's a very good reason to package these things together on the same machine: you can rely on local machine authentication to bootstrap the network authentication service. If the Kerberos secret store and the LDAP principal store are on different machines and you need both to authenticate network access, how do you authenticate the Kerberos service to the LDAP service?
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by Nextgrid on Wednesday February 18, 2026 @09:14AM (#47061134)
It's also a ton of security-sensitive code that parses untrusted data in a memory-unsafe language.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by nimbius on Wednesday February 18, 2026 @09:46AM (#47061500)
There used to be a time in history when a system administrator had to know all this shit in order to keep their job. I guess nowadays devops just means dev as we furiously pump tokens into the AI Wurlitzer whenever we dont know how to do something and hope it doesnt gaslight us into deleting prod.

- Freeipa is Linux AD, includes DNS, dogtag, and OpenLDAP.

- SSSD is how linux machines authenticate with a central directory. this includes AD.

- nss is the order of operations in which the system attempts lookups against various directories for services.

- pam is the subsystem of authentication in linux.

- kerberos is a ticket based authentication system started by MIT and popularized by Microsoft.

- ldap is a directory for information and authentication data

- DNS should not need an explanation.

Active Directory is the exact same byzantine architecture, the only reason you dont complain about it is because Microsoft has hidden nearly every meaningful internal from you with fun buttons and dropdowns like a childs toy.

Make no mistake, when it breaks it is much more cataclysmic in its complexity. major multinational corporations can spend weeks with external consultants and even Microsoft themselves trying to debug it. Most failure modes result in rebuilding the entire directory from scratch out of the sheer futility of trying to recover anything. things as simple as an OS update can cause the complete failure of the directory, replication, kerberos key subsystem, or even the ADUC tool you use to interface with any of this. Most of the time your only solution is to wait for MS to release a fix.

FreeIPA isnt complete. it doesnt include things like group policies or account expiration but its infinitely easier to debug. its individual components are well documented and offer standalone debug and trace features. most if its components have existed longer than their competitive Microsoft offerings, or at very least vastly outscale and outperform them.

Kubernetes is just as complex, but cloud providers will happily bill you by the nanosecond for the gentle equivalent of Microsofts buttons and dropdowns. Microsoft will gladly bill you for "cloud" based AD. You can just as easily deploy local users in ansible.

Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by p_ing on Wednesday February 18, 2026 @10:43AM (#47062195)
Dang, your failure modes certainly are extreme. What companies actually performed a from-scratch rebuild because they failed to take a backup or thought "today's thursday, it's too complicated to restore!"?

If an "OS upgrade" nukes your directory, that means you're running a single DC. The question is... why would you do that?

Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by linksnapzz on Wednesday February 18, 2026 @01:36PM (#47064482)
There used to be a time in history when a system administrator had to know all this shit in order to keep their job. I guess nowadays devops just means dev as we furiously pump tokens into the AI Wurlitzer whenever we dont know how to do something and hope it doesnt gaslight us into deleting prod.

Thanks, that sentence made my day.

Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by StopDisinfo910 on Wednesday February 18, 2026 @10:13AM (#47061849)
It's always been awful. OpenLDAP by itself is already attrocious and a pain to make work.

I have always been convinced it was on purpose. It's the point where you were supposed to decide paying Redhat is actually a good idea and nowadays it pushes towards a cloud based authentication solution you can integrate.

Realistically, who has any interest in fixing the mess?

Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by doctorpangloss on Wednesday February 18, 2026 @10:28AM (#47062049)
> Realistically, who has any interest in fixing the mess?

Okta is a multi billion dollar company, there is a lot of venture opportunity in this space.

Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by StopDisinfo910 on Wednesday February 18, 2026 @10:34AM (#47062122)
I think that's actually directly in agreement with what I said. Okta built their own thing on the side without touching the Linux stack and is very happy for you to turn to them. So did Authentik actually.
Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by xorcist on Wednesday February 18, 2026 @01:15PM (#47064214)
> you were supposed to decide paying Redhat

Fwiw, all Red Hat LDAP products are based on 389DS because they thought OpenLDAP had too many pain points or something.

Re:Native FreeBSD Kerberos/LDAP with FreeIPA/IDM by Smar on Wednesday February 18, 2026 @04:51PM (#47066950)
LDAP Kerberos 5 SSSD is pretty easy to configure and more or less maintenance free for a small set of servers and users. By my personal experience.

The costs usually come from complexity: every new user needs its credentials, guidance to services and help in error situations. New services need to be integrated to existing systems. But those won't go away, be the system anything.