sviperz

Can confirm, it's fixed in 6.12.6 (2759). UPD: nope, still have it on this version. UPD2: finally really fixed in 6.12.7 (2787).

Enpass 6.12.6 (2753, website version), macOS 27.2 (26B5086k), Apple Silicon. Since 6.12.6 added Secure Event Input, Enpass keeps macOS Secure Input enabled for as long as the vault is locked — not just while a password field has focus. Secure Input is a system-wide lockout, so for that whole period no other application can receive key events through a CGEventTap. Last night Enpass held it for nine hours straight with no Enpass window on screen. Your release note says the feature "prevents other apps from monitoring your keystrokes when sensitive password fields have focus". The actual behaviour is far broader. To reproduce: unlock Enpass and Secure Input turns off; close the main window with the red button, with "Autolock When > Main Window is Closed" enabled, and Enpass locks — Secure Input turns on and stays on until you unlock the vault again. The same happens via "System Inactive for" (mine was 1 minute): Enpass autolocks in the background and Secure Input goes on with no Enpass UI visible at all. That second variant is the one that looks like a random system fault. Measured with a 4 Hz poll of IsSecureEventInputEnabled(): the flag goes on 1 s after launch (the app starts locked), off on unlock, on again the moment the window is closed, and it is released only when the Enpass process exits — 13:48:53 here, to the second. This silently breaks text expanders, automation, dictation, accessibility tools and keyboard-layout utilities, with nothing on screen to say why. It is also hard to diagnose: kCGSSessionSecureInputPID records the FIRST process that raised the flag in an episode, so while Enpass holds it underneath, the record can name something unrelated like loginwindow. Please release the flag on window hide/close/minimise and on app deactivation, and tie it to the password field having focus. A locked vault with no visible window has no field to protect. KeePassXC hit the same failure mode with the same feature and treated it as high priority: https://github.com/keepassxreboot/keepassxc/issues/11906

Could you please consider one small visual change to the way the card numbers are displayed? Sometimes there is a need to type in card numbers manually. It is much easier to do when card numbers are delimited visually like XXXX XXXX XXXX XXXX. Can you please add default card number format options in the settings? Or maybe add additional Field Type as Card Number Delimited so everyone could choose? Of course, clipboard format must be without any spaces. Thanks!

Could you please add Auto or System default mode for theme, so the app can follow theme currently set in the system? This way it will be possible to use light/dark theme automatically depending on the theme in the system itself.