Skip to content

LDAPilot v0.6.0

Latest

Choose a tag to compare

@github-actions github-actions released this 13 Nov 08:07

This release is mostly about getting LDAPilot onto a computer and getting data in and out of a directory: real installers for Windows and Linux, an LDIF import that adapts a file instead of refusing it, and much shorter waits in large directories.

Installation

  • New Windows setup (Inno Setup, replaces the NSIS setup). It installs for all users (C:\Program Files\LDAPilot) or only for you without administrator rights (%LOCALAPPDATA%\Programs\LDAPilot), in German or English.
  • The setup runs unattended for software distribution: /VERYSILENT /ALLUSERS or /CURRENTUSER, a log with /LOG=, documented exit codes and a fixed uninstall key for detection rules.
  • A running LDAPilot is noticed, also in other Windows sessions and of other users on a terminal server. A silent setup then stops with exit code 7 instead of reporting success with the old file, the interactive setup offers to close it.
  • A missing WebView2 runtime is installed with Microsoft's bootstrapper (/WEBVIEW2=nodownload for networks without internet, /WEBVIEW2=ignore to skip it). The desktop shortcut is optional and off by default.
  • An installation for all users removes the 0.5.0 installation first. Your settings stay where they are.
  • Linux packages: .deb for Debian 12+ and Ubuntu 22.04+, .rpm for Fedora, openSUSE and RHEL 10, a separate .rpm for RHEL 9, and LDAPilot-linux-amd64.tar.gz with an install.sh that installs into ~/.local without root. They bring a desktop entry, icons and AppStream data, so docks and panels now show the LDAPilot icon for the window. The bare Linux binaries are no longer attached to releases.
  • The release files have the same name in every release (LDAPilot-linux-amd64.deb and so on), so the install commands in the README always fetch the newest version.
  • LDAPilot.exe carries complete version information for inventory tools.
  • docs/installation.md has the command lines, exit codes and detection rules for administrators (Intune, Configuration Manager, Ivanti DSM).

LDIF import and export

  • The import adapts a file instead of refusing it. A file from slapcat, from ldapsearch with +, from another kind of directory or exported without "Importable" used to fail at the first record. Attributes the server maintains itself (entryUUID, entryCSN, createTimestamp, objectGUID, objectSid, memberOf and the like) are now left out, and so are attribute types and object classes the target server does not know. The dry run says per record what was left out and why.
  • You decide once for the whole file, before the run:
    • entries that already exist: skip (default), update or report as an error
    • attributes the server maintains: leave out, or send them. OpenLDAP then really keeps entryUUID, the timestamps and the password history. For 389 Directory Server and Active Directory the dialog says beforehand that they assign IDs and timestamps themselves.
    • unknown attributes and object classes: leave out or send
    • on Active Directory, references to entries that do not exist (member, manager): leave out or send
  • The choices are remembered.
  • The dry run now predicts for new entries what the server will refuse: missing required attributes, several values in a single-valued attribute, unicodePwd over an unencrypted connection. Entries below an entry that could not be created are no longer sent.
  • On Active Directory a group that stands in the file before its members gets them at the end of the run instead of failing.
  • Passwords: hashes from the file are imported, with the connection's storage policy or exactly as in the file. Questions about them come once before the run, not as failed records. The dialog explains what cannot work (unicodePwd without TLS, and that an Active Directory export contains no passwords).
  • "Continue after a failed record" is on by default.
  • Faster with many entries. Measured with 100,000 users on OpenLDAP: the export is written straight to the file (about 10 s, before 15 s plus half a minute in which the window was busy), the dry run takes 16 s instead of 30 s, the import 41 s instead of 77 s. A large import in the dialog took 6 minutes and now takes 71 s, because the window no longer lags behind the server.
  • 389 Directory Server role membership (nsRoleDN) is no longer dropped from "Importable" exports.

Large directories

  • Opening the Contents list of a container with 40,000 entries shows the first rows after about 1 s. Before it took about 100 s. Reading from the server was never the slow part, the time was lost in the window.
  • Scrolling the tree and the lists renders only rows that changed.
  • The tree sorts by type, then by name by default.

Accounts and passwords

  • Set Password for LDAP persons without a login (OpenLDAP, 389 Directory Server). A person without uid and without a password is shown as a contact and had no password command, so it could never get the password that makes it a user. Such entries now offer Set Password wherever users have Reset Password. After the write the entry is shown as a user with the Account tab, without a refresh. Not on Active Directory, where contact objects cannot have a password.
  • SASL pass-through authentication (userPassword: {SASL}user, follow-up to #1). Such a reference has been stored unchanged by every write path since 0.5.0. Only Reset Password hashed whatever was typed. It now recognises a typed {SASL} reference or an already hashed value, says what it is and offers "Store as Typed". Resetting an account that uses pass-through authentication warns that the reset replaces the reference with a local password.

AI assistant

  • Claude Code in WSL (Windows). The Claude Code engine also works with a Claude Code that is installed only inside a WSL distribution. The AI settings let you choose where it runs: Automatic (a Claude Code for Windows wins, else WSL), Windows, or WSL with the distribution. claude is found as in your terminal, also when it comes from nvm or npm. Nothing listens outside this computer and no firewall rule is needed.
  • This part is new and was tested against a simulated WSL only. If it does not work on your Windows, please open an issue.

Known limitations

  • The builds are still not code-signed. Windows SmartScreen may ask once ("More info", then "Run anyway"). On macOS the app is not notarized.
  • The macOS build is made by CI and was not tested on a Mac by hand.

Downloads

Platform File For
Windows (amd64) LDAPilot-windows-amd64-installer.exe Setup for all users (administrator, software distribution) or just you (no admin rights); silent with /VERYSILENT /ALLUSERS or /VERYSILENT /CURRENTUSER. Installs the WebView2 runtime if it is missing.
LDAPilot-windows-amd64.exe Portable, nothing installed
Linux (amd64) LDAPilot-linux-amd64.deb Debian 12+, Ubuntu 22.04+
LDAPilot-linux-amd64.rpm Fedora, openSUSE, RHEL / Rocky / Alma 10 (with EPEL)
LDAPilot-linux-amd64.el9.rpm RHEL / Rocky / Alma 9
LDAPilot-linux-amd64.tar.gz Any distribution, just you without root: unpack and run ./install.sh
macOS (Apple silicon + Intel) LDAPilot-macos-universal.zip Not notarized: open it once via System Settings › Privacy & Security › Open Anyway

The builds are not code-signed. Command lines, exit codes and detection rules for software distribution: docs/installation.md. Checksums: SHA256SUMS.txt. Full changelog: CHANGELOG.md