gnoMint

A GTK 4 Certification Authority manager

View the Project on GitHub davefx/gnoMint

Installing gnoMint

From distribution packages

gnoMint has historically shipped in Debian and Ubuntu. The packaged version may lag the upstream release; check packages.debian.org or your distribution’s equivalent.

# Debian / Ubuntu
sudo apt install gnomint

# Fedora (when available)
sudo dnf install gnomint

For recent releases (the 1.6.x “Tempered Anvil” series and newer), you’ll likely want to install via Flatpak or build from source.

Flatpak

The easiest way to run the latest gnoMint on any Linux distribution:

# Build and install from the repo manifest
flatpak-builder --install --user build-flatpak \
    net.sourceforge.gnomint.yml

# Run
flatpak run net.sourceforge.gnomint

The Flatpak bundles GnuTLS, libgcrypt, and all other dependencies inside the sandbox. It uses the GNOME 48 runtime for GTK 4.

Windows

Every release ships a Windows installer, gnomint-<version>.msi, attached to the corresponding GitHub Release. It is a 64-bit build produced with MSYS2/MinGW and packaged with the WiX Toolset.

1. Download gnomint-<version>.msi from the Releases page.
2. Double-click it and follow the installer.
3. Launch "gnoMint" from the Start menu (the GUI), or run
   "gnomint-cli" from any terminal — the installer adds it to PATH.
4. .gnomint database files are associated with the GUI, so you can
   open a CA database by double-clicking it.

The installer is self-contained: it bundles GTK 4, GnuTLS, libgcrypt, SQLite, the GDK-Pixbuf image loaders, and the icon theme, so no MSYS2 or separate GTK runtime is required.

The Windows build is verified in CI by launching the bundled GUI on a clean Windows runner on every change, but it sees far less real-world use than the Linux builds. If something doesn’t work, please open an issue.

Building from source

Dependencies

gnoMint links against:

Build-time tools:

On Debian/Ubuntu the full set installs with:

sudo apt install \
    build-essential autoconf automake libtool intltool pkg-config \
    libgtk-4-dev libglib2.0-dev libgnutls28-dev libgcrypt20-dev \
    libsqlite3-dev libreadline-dev

The same package list is used by gnoMint’s CI workflow, so it stays in sync with what upstream tests against.

Configure, build, install

From a git checkout:

./autogen.sh        # only after a fresh clone
./configure         # add --enable-debug for -g -O0
make
sudo make install

From a release tarball, skip autogen.sh and start at ./configure.

The build produces two binaries:

Both are installed into $prefix/bin (default /usr/local/bin). UI files, icons, and translations go to $prefix/share/gnomint/, $prefix/share/icons/, and $prefix/share/locale/ respectively.

Running tests

make check

The suite runs Y2K38 unit tests, a static .ui consistency checker, a Wayland-backed workflow regression test (started by tests/run-headless.sh via weston), and CLI smoke tests. See the features page for what’s covered.

First run

On first launch gnoMint creates an empty database at $XDG_DATA_HOME/gnomint/default.gnomint (typically ~/.local/share/gnomint/default.gnomint). Existing databases at the legacy ~/.gnomint/default.gnomint location are migrated automatically.

From there, see the user manual for the first-CA walkthrough.

Reporting build failures

If ./configure or make fails, please file a bug at github.com/davefx/gnoMint/issues including: