• v1.32.1 776f372834

    LDAP WebGUI v1.32.1
    All checks were successful
    Tests / pytest (newest CPython, warning only) (push) Has been skipped
    Tests / Scope (push) Successful in 3s
    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 25s
    Tests / pytest (Python 3.11) (push) Successful in 19m38s
    Tests / pytest (Python 3.13) (push) Successful in 20m42s
    Tests / Publish release (push) Successful in 4s
    Stable

    Lyra released this 2026-11-07 09:44:05 +01:00 | 6 commits to main since this release

    Security

    • A password re-check that binds on another entry ends the session.
      Change-password, 2FA disable/replace and the admin re-checks confirm
      the current password by a bind, but the password write then went to
      the DN the login had bound with. Had another tool moved the account
      by modrdn after the login and put a different entry at the old DN,
      the new password landed on that entry. The re-check now compares the
      DN it bound with against the session's (normalised: case and spaces
      around separators aside); if they differ, the session ends, nothing
      is written, and REAUTH_IDENTITY_CHANGED is logged — without
      counting toward the re-authentication limit. Sessions from before
      1.32.1 carry no DN and are not compared.

    • A uid or cn in the path addresses exactly its entry. 1.32.0
      stopped the path guards from rewriting a name (/users/a%2Cb had
      shown and saved ab, a 65-character uid its 64-character prefix) by
      refusing every name they would have changed with 400. The name is now
      used as it came: the LDAP layer looks it up escaped and answers only
      for the entry that carries exactly that name (case aside), so a,b
      opens and edits a,b, never ab, through every per-entry route
      (edit, delete, password reset, SSH keys, sudo toggle, group members,
      sudo rules). A name no entry can carry (control characters, over 256
      characters) is still a 400.

    • A name the directory folds onto another entry no longer reaches it.
      slapd matches uid and cn ignoring leading, trailing and repeated
      spaces and compatibility characters, so POST /users/%20alice/reset-password
      (or alice%20) set alice's password, logged uid= alice, and for
      a b left the sessions of a b alive. Every lookup of an existing
      account, group or sudo rule now answers only for the entry whose own
      name is the one asked for (ASCII case aside — the Kelvin sign K no
      longer counts as k), the password reset has no fallback to a
      constructed DN, and group membership checks compare memberUid
      values exactly (the server folds spaces there too). The password
      reset, user delete and sudo grant/revoke log the entry's own uid, and
      the reset ends the sessions keyed on it.

    • A trailing newline no longer passes the name validators. They used
      re.match with $, which also matches before a final \n — abc\n
      was a valid group name. Every anchored validator now uses fullmatch
      (uid, cn, group cn, email, the login username, settings, the docs
      viewer, the update/access/certificate runner inputs, the monitoring
      token hash).

    • Control characters in sudo rules are refused. A NUL, ESC, DEL or
      any other control character inside a sudoUser, sudoHost,
      sudoCommand, sudoRunAsUser, sudoRunAsGroup or sudoOption value
      was stored — the textarea is split at line breaks, and NUL, ESC or DEL
      are none — and reached sssd and sudo as part of the rule. Each value
      now has a length bound (sudoCommand 4096, sudoHost 255, sudoOption
      1024, the others 256) and each attribute a count (128 values,
      sudoOption 64). The checks run in the LDAP layer too, not only in the
      form.

    • description is bounded on users, service accounts, groups and sudo
      rules
      : at most 1024 characters per value (the schema's bound),
      control characters other than tab and line breaks refused. A value
      starting with the prefix the two-factor configuration is stored under
      is now refused on create too, not only on edit.

    • A refused login name is cut in the log. The name that failed the
      username check went into app.log whole, before the login limiter
      counted the attempt — one request could write up to the body limit.
      It is now cut at 64 characters with control characters masked. An
      X-Real-IP that is not an IP address is ignored in favour of the
      peer address, so it cannot carry a long value or a forged | key=…
      into the security log either.

    • Request bodies are limited to 1 MiB. Werkzeug applies its form
      memory limit only to multipart forms, so every other form field
      reached the application at nginx's 10 MB. A larger request now gets a
      413 page ("too large — nothing was saved"); an htmx request is sent
      back to its page with that message. The rest of a refused body (up to
      nginx's 10 MB) is read and discarded before the answer, so nginx gets
      the 413 instead of a reset connection and a 502; a larger or chunked
      body is not read and the connection is closed.

    • A fresh install no longer downgrades Pillow to 11.1.0. Since
      v0.8.1 install.sh installed pyotp, qrcode, Pillow==11.1.0 and
      ruamel.yaml a second time with its own versions after
      requirements.txt, which pulled Pillow back from the pinned 13.0.0 to
      a release with many published advisories — and the dependency checks,
      which read requirements.txt, could not see it. The installer now
      only checks that these packages import; requirements.txt is the only
      place a version is named, and a test keeps every script free of
      package versions. Operators: a host installed with install.sh
      since v0.8.1 and not updated since runs Pillow 11.1.0 — check with
      /opt/ldap-webgui/venv/bin/pip show pillow; an update (Settings →
      Update, or sudo ldap-webgui-update) installs 13.0.0.

    • New passwords have an upper bound and no NUL. At most 511 bytes
      (UTF-8) — the longest answer Linux-PAM passes on, so longer ones
      worked in the WebGUI but at no login prompt — and no NUL character,
      for the own change, a reset, a create and the CSV import. The login
      takes any length but refuses a NUL before the bind.

    Fixed

    • Entries with an unusual uid or cn open again. A uid such as (x),
      #lead, fz inner, one with umlauts or other non-ASCII characters,
      or one longer than 64 characters — written by another tool — was
      listed but could not be opened: before 1.32.0 its link answered
      "User not found" for a mangled name, 1.32.0 refused it with 400. The
      detail, edit and delete pages and every route behind them reach it
      again; new names keep the strict charset.

    • Line breaks and malformed values in single-line account fields are
      refused.
      User and service-account create and the user edit stored
      CR/LF in givenName, sn, mail, title, telephoneNumber,
      homeDirectory and loginShell, any string as loginShell (10 000
      characters, no path), and any length as homeDirectory. The forms and
      the LDAP layer now require one line, loginShell an absolute path
      without whitespace (max 255), homeDirectory an absolute path (max
      1024). A value already stored that the form sends back unchanged does
      not block an edit.

    • gidNumber on accounts is range-checked. Create and edit stored
      -1, 2147483648 or 10^20; a non-numeric value became 1000 on
      create and was ignored on edit. Both now answer "gidNumber must be a
      number between 1 and 65534", and an empty field on create still means
      1000. 0 (root's group) is refused as a new value — see Upgrade notes.

    • A non-ASCII sudoHost/sudoCommand/sudoOption value is refused
      by the form
      with the field's name and the reason (IA5String), instead
      of the raw ldap3 "invalid per syntax" message. sudoUser,
      sudoRunAsUser and sudoRunAsGroup are DirectoryString in the sudo
      schema and take any character but a control character, so a name with
      an umlaut can be referred to.

    • Removing many group members at once answers with one message per
      outcome.
      Selected values that are not members are reported together
      and cost no LDAP write (1000 of them made 1000 "check LDAP logs"
      flashes and 1000 modifies); failed removals are summarised too, and
      long name lists are cut after ten.

    • A gidNumber of thousands of digits no longer causes a 500. The
      user create and edit forms passed it to int(), which raises past
      4300 digits; a sudoUser of # plus such a number (or #²) did the
      same on the Machines pages. IDs are now read as at most ten ASCII
      digits and refused otherwise.

    • The CSV preview checks what the import will check. A row with a
      line break in title, an over-long name, a homeDirectory containing
      a newline or a loginShell with a tab was green in the preview and
      failed at commit, after the other rows had been written. The preview
      now applies the same account rules as the import, for new and for
      updated accounts. Control characters, for every single-line field,
      include C1 characters (U+0080–U+009F) and U+2028/U+2029.

    • Automatic ID assignment names the size limit. When the scan for
      the next free uidNumber/gidNumber is cut by the directory's size or
      time limit, the create (and the CSV import) now says so and points at
      olcLimits in docs/ldap-acl-setup.md, instead of "check the read
      permissions and the ID range".

    • An admin that is no posixAccount can sign in and change their
      password again.
      The exact lookup earlier in this release only finds
      posixAccounts, so an inetOrgPerson admin listed as member of a
      groupOfNames admin group was refused (or read-only) and
      /change-password answered "not found". The login now keeps the DN
      its bind succeeded with in the session; the group check and the own
      password change use it. Sessions from before the update keep working.
      A password reset of another account still resolves exactly.

    • A CSV export re-imported as an upsert no longer fails on old
      values.
      A title over 128 or a telephoneNumber over 64 characters
      written by another tool failed the preview and the commit although
      nothing would have been written. Update rows are now checked on what
      differs from the stored entry, as the edit form does; new accounts
      are still checked in full.

    • A failed account-type lookup at login is logged as such. It is
      still refused, but as LOGIN_FAILURE | reason=account_type_unreadable
      instead of reason=service_account.

    • A user or group edit request without a field no longer clears it.
      A POST that did not carry mail, title, telephoneNumber or
      description removed those attributes and reported success; only a
      field sent empty clears its attribute now.

    • A CSV file with a cell over 128 KiB no longer causes a 500. The
      csv module's error is answered with "The file could not be read as
      CSV", without quoting the file.

    • Group gidNumber and sudoOrder are read as plain decimals. Both
      went through int(), which takes 1_000, +5 and Arabic-Indic
      digits. The gid range is also checked by the LDAP layer's group
      create, not only by the form.

    • A sudo rule with a sudoOrder above 999 can be edited again. Rules
      written by cvtsudoers or another tool often carry one; the form
      pre-filled it and the save refused it. The range applies to a new or
      changed value only, and so do the new value rules above — a rule
      with a longer command keeps saving as long as that command is
      unchanged.

    • An account with an SSH key another tool wrote can be edited
      again.
      A stored key with command= or no-pty failed every save of
      the key list, because the whole set was checked; keys the account
      already holds are no longer checked again. A new key still accepts
      from= only.

    • A CSV import refused as a whole is logged with its rows as failed.
      An import stopped before the first write (the uidNumber scan at the
      size limit, no free uidNumber) logged CSV_IMPORT_COMMIT with
      failed=0; the rows that were not written now count as failed=.

    Upgrade notes

    • Pillow: a host never updated since its install.sh run has
      Pillow 11.1.0 (see Security); this update replaces it.
    • No vhost change. nginx keeps client_max_body_size 10m; the
      application refuses anything over 1 MiB itself (the largest legitimate
      request is the CSV import, 512 KiB).
    • New account and group names — the create forms, the CSV import's
      new rows, service accounts, manage.py create-admin — must be at most
      32 characters of lower-case letters, digits, ., _ and -,
      starting with a letter or _. That is what useradd/groupadd
      accept by default (NAME_REGEX), utmp's 32-byte ut_user is where
      longer names get cut in who/last, and an @ is read as
      user@domain by sssd. Existing accounts and groups are untouched:
      they sign in, open, are edited, added as members and named in sudo
      rules as before, upper case and @ included.
    • gidNumber 0 (root's group) can no longer be given to an account
      as its primary group — on create, edit or in the CSV import. An
      account that already has it stays editable as long as the gidNumber
      is left as it is. Groups with gidNumber 0 are not affected.
    • New passwords are limited to 511 bytes (UTF-8) and must not
      contain a NUL. Existing passwords are untouched and still sign in,
      whatever their length.

    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