-
LDAP WebGUI v1.25.1
StableAll checks were successfulTests / pytest (Python 3.11) (push) Successful in 2m39sTests / pytest (Python 3.12) (push) Successful in 2m46sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 17sRelease / Publish release (push) Successful in 2sreleased this
2026-11-02 01:35:16 +01:00 | 18 commits to main since this releaseSecurity
- StartTLS checks the directory's certificate. With
tls.start_tls: trueon port 389 and notls.ca_cert, the connection was encrypted
but any certificate was accepted —tls.verifywas ignored, so an
attacker in the path could read the bind password and every login
password. It now verifies against the system trust store (or
ca_cert), as LDAPS always did. Check before updating: a directory
whose certificate the system does not trust now refuses the connection
— add its CA to/usr/local/share/ca-certificates/(then
update-ca-certificates) or settls.ca_cert. - Deleting a user removes their group memberships and sudo rules
first.memberUid,member/uniqueMemberandsudoUserentries
used to stay behind, so a new account created later under the same uid
inherited admin rights and sudo. If a reference cannot be removed the
account is not deleted and the page names the group or rule. - Group members are written as the directory spells the uid.
memberUidcompares case-sensitively, so addingJDoefor the account
jdoesilently granted nothing. - Your own account cannot be deleted under another spelling of your
uid. - The installer and the updater no longer follow a symlink at the
session store./var/lib/ldap-webguibelongs to the service user, so
code running as that user could replacesessionswith a link, and the
next install or update, running as root, set the link's target to 0700
(/etcor/usr, breaking the host). Both now refuse a symlink there
(the update fails at the state step and is rolled back) and create the
directory and set its mode as the service user. - One account, one 2FA lockout, whatever the spelling. The directory
matches user names case-insensitively, soAdminsigned in asadmin
— but the 2FA lockout and the guard against reusing a code were kept
per spelling. Every case variant got a fresh budget of 20 guesses
(defeating the permanent lock) and an observed code could be replayed
asADMIN. After the password check the login now uses the user name
as stored in the directory, for the session, the role check, the
lockouts and the log; the lockout stores ignore case, existing state
files included.manage.py unlock-totp,disable-2faand
set-passwordresolve the stored name too. - A successful login no longer wipes the failed attempts against other
accounts. The login limiter dropped an address's whole record on any
successful login, so someone with an account of their own could guess
another account's password without limit — four wrong guesses, one
correct login of their own, repeat. A success now takes back only the
failures counted for the account that signed in. - Changing your password signs out your other sessions. So do
disabling or replacing 2FA, an admin resetting your password (in the UI
or through a CSV import) and a reset withmanage.py: a
session opened with the old password ends on its next request (the
session that made the change stays signed in for the 2FA actions). The
change times are kept in/var/lib/ldap-webgui/credential_epochs.json. - The current-password check on change-password, 2FA disable and 2FA
replace is rate-limited. Someone holding a stolen session could try
passwords there as fast as the directory answered. Wrong passwords are
now counted per account with the login limit and lockout time; reaching
the limit signs the session out and is logged (REAUTH_LOCKOUT; an
attempt while locked isREAUTH_BLOCKED). State file:
/var/lib/ldap-webgui/reauth_lockouts.json. - Parallel requests no longer get extra guesses past a lockout. Both
the login limiter and the 2FA lockout checked and counted an attempt in
two steps, so requests already in flight were all evaluated when the
limit was reached. Checking and counting is now one locked step taken
before the password or code is verified. - A backup code works once, even when sent twice at the same time.
Two parallel verifications could both accept the same code, and a stale
write could bring back a code another request had just used. When the
directory refuses to mark the code used because it has already changed,
the attempt counts as a wrong code.
Upgrade notes
- StartTLS without
tls.ca_certnow verifies the certificate (see
Security) — a directory with an untrusted certificate stops working
until its CA is trusted. LDAPS and setups withca_certare unchanged. - Session store: if
/var/lib/ldap-webgui/sessionswas replaced by a
symlink on purpose, the update now stops and rolls back — set
LDAP_WEBGUI_SESSION_DIRinstead. - No
nginx/ldap-webgui.confchange.
Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
sudo bash <extracted-dir>/update.sh --archive <tarball>Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- StartTLS checks the directory's certificate. With