• v1.33.0 b48ad7042d

    LDAP WebGUI v1.33.0
    All checks were successful
    Tests / Scope (push) Successful in 1s
    Tests / pytest (newest CPython, warning only) (push) Has been skipped
    Tests / 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 1m22s
    Tests / pytest (Python 3.13) (push) Successful in 21m9s
    Tests / pytest (Python 3.14) (push) Successful in 22m30s
    Tests / Publish release (push) Successful in 3s
    Stable

    Lyra released this 2026-11-08 19:02:50 +01:00 | 4 commits to main since this release

    Upgrade notes

    • The nginx vhost is now replaced by every update.
      /etc/nginx/sites-available/ldap-webgui is the application's file:
      rendered from the shipped template and the new host settings file
      /etc/ldap-webgui/vhost.env, checked, installed, confirmed served,
      and put back if anything fails. Local edits to the vhost are lost —
      host names, certificate paths and listen addresses belong in
      vhost.env, who may connect stays Settings → Access.
    • The first update migrates: it reads those values from the
      installed vhost and writes vhost.env; the previous file stays as
      /etc/nginx/sites-available/ldap-webgui.pre-<version>.
    • A vhost edited by hand is not touched — no rollout, a manual step
      that lists the differing lines, repeated by every update — until you
      carry over what you need and run
      sudo ldap-webgui-update --vhost-only --replace-vhost.
    • Git mode (sudo ldap-webgui-update) and
      ldap-webgui-update --archive need a second step:
      they run the
      previous release's update.sh, which does not know the vhost yet.
      Afterwards run sudo ldap-webgui-update --vhost-only (after
      --archive: sudo bash <unpacked release>/update.sh --vhost-only).
      The web update, --from-release and an unpacked release's own
      update.sh do it in one run.
    • The steps, how to check, how to back out and the downgrade:
      docs/upgrade-1.33.md (also under Settings → Documentation).

    Added

    • /etc/ldap-webgui/vhost.env (root:root 0640) — the vhost's host
      settings: SERVER_NAME, TLS_CERT, TLS_KEY, LISTEN. Parsed,
      never sourced; an invalid file or an unknown key skips the rollout
      with a manual step and never fails the update.
    • update.sh --vhost-only re-renders the vhost from vhost.env and
      the installed release — checked, nginx -t, reloaded, confirmed, the
      previous one put back on failure; no release change, no restart of the
      WebGUI. The way to apply an edited vhost.env.
    • A change of the listen addresses restarts nginx (the update,
      --vhost-only, install.sh): a reload cannot move nginx between
      "every address" and given ones — it keeps the old sockets and still
      reports success. Same addresses: a reload, as before.
    • update.sh --replace-vhost replaces a hand-edited vhost from
      before 1.33.0 (the previous file is kept).
    • install.sh --server-name "NAMES" and --listen "ADDRS" set
      SERVER_NAME and LISTEN at install time. With LISTEN set, nginx
      listens on those addresses plus 127.0.0.1 (the health checks use
      loopback).
    • /health answers with an X-LDAP-WebGUI-Vhost header — the hash of
      the rendered vhost, which the update and the installer use to confirm
      nginx serves the new one.

    Changed

    • The security headers reach the static files. The locations for
      /static/ and /health set headers of their own, and nginx then drops
      every header set at server level: CSP, X-Frame-Options,
      Referrer-Policy and Permissions-Policy were missing on stylesheets,
      scripts and images. Every such location now carries the full set.
    • /robots.txt sends one Content-Type instead of two.
    • The vhost template's comments are English, its header says it is
      overwritten by every update, the cipher list is labelled Mozilla
      intermediate; /health is proxied with Connection "" like the rest.
    • A re-run of install.sh replaces a differing vhost — an older
      release's or one edited by hand — after keeping it as
      ldap-webgui.pre-install-<timestamp>; host names, certificate paths
      and listen addresses are carried over into vhost.env. Up to 1.32 it
      kept any vhost that included the access list.
    • install.sh and the update take the access list lock and then the
      certificate lock before touching nginx, so an access list change or a
      certificate renewal from the web UI never runs into a vhost change.
    • The web update's One manual step is left box shows why the vhost
      was not replaced, the lines a hand edit added, and the command the
      update itself prints for that case (--replace-vhost, the ln -sfn
      line, or the lines that put the previous vhost back).
    • install.sh reports a vhost nginx does not serve as a failed check
      and ends INCOMPLETE (exit 1) instead of "All checks passed".
    • install.sh refuses a vhost.env that is not root's alone (a
      symlink, another owner, group- or world-writable) before installing
      anything — the update skips the rollout for it.
    • The vhost's structure check also refuses return, rewrite and if
      (they act before the access list) apart from the template's redirect
      and robots.txt answers, and error_page with = or a named target.

    Removed

    • The update's vhost drift warning ("The installed nginx vhost differs
      from the one this release ships"
      ) — the update replaces the vhost
      instead.
    • The NGINX_VHOST_FILE environment override of update.sh; the vhost
      is always /etc/nginx/sites-available/ldap-webgui.

    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