Samba 2020: Why are we still in the 1980s for authentication?
summary
Samba 4.11 scales to 300,000 users in simulated load tests, moves to Python 3, adds CI via GitLab, disables disabled SMB1 by default and removes DES while adding fuzz testing; yet authentication still relies on NTLM/NTLMv2 and Kerberos with awkward Windows constraints. Proposals include tunneling auth over SSH using libssh, embedding a KDC on file servers, salting legacy NTLM hashes, slipping TOTP/one‑time tokens into the protocol, or pairing Samba with Keycloak for web‑style identity federation.
AI-written summary · about
chapters (5)
related talks
54mState of authentication and identity in Fedora
26mWho Authenticates Linux? Rethinking PAM & NSS in the Age of Cloud Identity
32mPasswordless Auth: a JSON-Based Approach for modern authentication w/ SSSD & GNOME
53mThe Importance of Identity-Centric Security in 2024
46mBack to the Roots of Single Sign-On: Kerberos
31mThe SMB Report Card
22mSemi-Advanced Threats vs the Semi-Critical Infrastructure
30mWhere we’re going… we won’t need passwords
