-
LDAP WebGUI v1.34.0
StableAll checks were successfulTests / pytest (newest CPython, warning only) (push) Has been skippedTests / Scope (push) Successful in 2sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh, config-backup.sh, certtool.sh, accesstool.sh) (push) Successful in 33sTests / pytest (Python 3.13) (push) Successful in 22m2sTests / pytest (Python 3.14) (push) Successful in 23m30sTests / Publish release (push) Successful in 4sreleased this
2026-11-09 19:43:42 +01:00 | 3 commits to main since this releaseUpgrade notes
- The nginx vhost changes, and the update rolls it out by itself — no
manual step. What nginx does differently afterwards:- TLS 1.3 only. Browsers, curl and Zabbix's HTTP agent with
OpenSSL 1.1.1 or newer connect as before; a poller on an older TLS
library no longer does (docs/monitoring.md→ Troubleshooting). - Stricter headers: a Content-Security-Policy without
'unsafe-inline'and withobject-src 'none';
Cross-Origin-Opener-PolicyandCross-Origin-Resource-Policy
same-origin; a widerPermissions-Policy;X-XSS-Protectionis
no longer sent. - Login rate limit in nginx:
POST /loginandPOST /2fa/verify
at 10 a minute per client address, a burst of 20 — over it nginx
answers 429 with its own page. Opening the login page is not counted. - The app gets
Hostas nginx's normalised name, and
X-Forwarded-Forholds the client address only.
- TLS 1.3 only. Browsers, curl and Zabbix's HTTP agent with
- Downgrade to 1.33.0: its update renders 1.33's own vhost. If that
rollout fails or is skipped (a lock still held, …), the 1.33 web UI
runs under the new CSP, which blocks its inline scripts — it stays
broken untilsudo ldap-webgui-update --vhost-only.
Added
- HSTS, set on the command line only:
install.sh --hsts 300|86400|31536000/--no-hsts, orHSTSandHSTS_MAX_AGEin
/etc/ldap-webgui/vhost.envplus--vhost-only. Never
includeSubDomainsorpreload. Refused while the certificate does
not verify for every server name against this host's trust store
(self-signed refused even when trusted); an update then renders the
vhost without HSTS and names the manual step. Settings → Certificates
shows the state read-only.docs/upgrade-1.33.md, section 9: the
lockout cases, the way back (browsers keep the policy until max-age
runs out), the IP-address emergency route. - While HSTS is on, a new nginx certificate that does not verify is
refused — by the certificate runner, and for an upload with its key
already in Settings → Certificates, before the password is asked for.
Changed
- The web UI has nothing inline any more — no inline scripts, event
handlers,<style>blocks orstyle=attributes — so the CSP needs
neither'unsafe-inline'nor hashes. Markdown tables (docs, release
notes) align withalign=.
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
- The nginx vhost changes, and the update rolls it out by itself — no