Skip to content
View in the app

A better way to browse. Learn more.

Enpass Discussion Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

brianhelfrich

Members
  • Joined

  • Last visited

  1. Still very much wanted on Linux. Here are some specifics that might help move it along. The standard way to do this on Linux is polkit, and the other big password managers already ship it. 1Password, Bitwarden and KeePassXC (Polkit Quick Unlock, in 2.8) all unlock through polkit. polkit hands the check to PAM, so the user’s existing system configuration decides what’s accepted: fingerprint via pam_fprintd, password, or a security key. The app never handles biometric data; it just gets a yes or no back. It wouldn’t change Enpass’s security model. Quick Unlock with a PIN already works this way: the master password is required at app launch, and after that a short check releases the key held in memory. A polkit check could stand in for the PIN prompt; no new key storage or cryptography is needed. 1Password describes its Linux implementation exactly like this (“stays in the memory while 1Password is running… removed from memory when you quit”). What it takes: a .policy file shipped in the package, plus a D-Bus call to org.freedesktop.PolicyKit1.Authority.CheckAuthorization. Enpass already uses D-Bus on Linux (logind, KWallet, Secret Service), so the plumbing is there. A question for the team: the Linux build I’m running (6.12.6.2258, Fedora 44, KDE Plasma 6) already contains the string “Unlocks Enpass using the biometrics on your Linux system.” Is Linux biometric unlock actively being worked on, and is there a rough timeline? I’m always happy to test.
  2. さちょこ79 started following brianhelfrich
  3. Confirming issue has been resolved in v6.11.10. Thank you kindly.
  4. Safari browser on the new iOS 18.4 betas do not correctly acknowledge licensed version of Enpass 6.11.8 and 6.11.9. Can manually type password to log into Enpass and settings does show Premium license. Attempting to use Enpass in Safari shows no results except first 10 / trial mode error message. Presenting as same (or similar) issue that occurred during past iOS updates. if more details are required to troubleshoot, I am happy to provide them. Thank you kindly.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.