Name: OTPClient
Author: Paolo Stivanin

Application for managing TOTP/HOTP tokens with built-in encryption

OTPClient is a secure and easy-to-use desktop client for TOTP and HOTP one-time passwords, built with GTK4 and libadwaita. Features:

multiple databases with sidebar management and cross-database search
token grouping with quick filtering
desktop search provider for GNOME Shell and KDE KRunner (opt-in trigger keyword)
command-line companion (otpclient-cli) with scriptable table/JSON/CSV output
support for TOTP, HOTP, and Steam codes
configurable digits (4 to 10), period (1 to 120 seconds), and algorithm (SHA1, SHA256, SHA512)
import and export of encrypted/plain Aegis backups
import and export of encrypted/plain Authenticator Pro and 2FAS backups
import and export of plain FreeOTP+ backups (key URI format)
import of Google Authenticator migration QR codes (file, screen, webcam, clipboard)
integration with the OS secret service provider via libsecret (opt-in)
local database encrypted with AES-256-GCM and Argon2id key derivation; plaintext lives only in libgcrypt secure memory while unlocked

Bug-fix release. A database stored on a filesystem that does not implement POSIX file locks, most notably the Flatpak XDG document-portal path (/run/user/UID/doc/) that the file chooser hands back, could not be opened or created and failed with "Failed to acquire database lock: Function not implemented"; the lock file added in 5.1.4 is now treated as best-effort. This release also stops the secure-memory pool from reserving the whole locked-memory budget, which had left the GTK password entry unable to lock its own buffer on every unlock.

FIX: a database stored on a filesystem without lock support (the Flatpak document portal, and some NFS/SMB mounts) could not be opened or created, failing with "Failed to acquire database lock: Function not implemented". Locking is now best-effort so the database opens normally on those filesystems, while real locking is unchanged everywhere else (#466)
FIX: the secure-memory pool consumed the whole RLIMIT_MEMLOCK budget, so the GTK password entry could not lock its own buffer and warned "couldn't lock 16384 bytes of memory (gtk): Cannot allocate memory", falling back to unlocked memory for the typed password on every unlock; the pool now leaves headroom for it (Debian #1141809)

Application for managing TOTP/HOTP tokens with built-in encryption

OTPClient is a secure and easy-to-use desktop client for TOTP and HOTP one-time passwords, built with GTK4 and libadwaita. Features:

multiple databases with sidebar management and cross-database search
token grouping with quick filtering
desktop search provider for GNOME Shell and KDE KRunner (opt-in trigger keyword)
command-line companion (otpclient-cli) with scriptable table/JSON/CSV output
support for TOTP, HOTP, and Steam codes
configurable digits (4 to 10), period (1 to 120 seconds), and algorithm (SHA1, SHA256, SHA512)
import and export of encrypted/plain Aegis backups
import and export of encrypted/plain Authenticator Pro and 2FAS backups
import and export of plain FreeOTP+ backups (key URI format)
import of Google Authenticator migration QR codes (file, screen, webcam, clipboard)
integration with the OS secret service provider via libsecret (opt-in)
local database encrypted with AES-256-GCM and Argon2id key derivation; plaintext lives only in libgcrypt secure memory while unlocked

FIX: a database stored on a filesystem without lock support (the Flatpak document portal, and some NFS/SMB mounts) could not be opened or created, failing with "Failed to acquire database lock: Function not implemented". Locking is now best-effort so the database opens normally on those filesystems, while real locking is unchanged everywhere else (#466)
FIX: the secure-memory pool consumed the whole RLIMIT_MEMLOCK budget, so the GTK password entry could not lock its own buffer and warned "couldn't lock 16384 bytes of memory (gtk): Cannot allocate memory", falling back to unlocked memory for the typed password on every unlock; the pool now leaves headroom for it (Debian #1141809)

OTPClient

Application for managing TOTP/HOTP tokens with built-in encryption

Changes in version 5.1.5

Links

OTPClient

Application for managing TOTP/HOTP tokens with built-in encryption

Changes in version 5.1.5

Links