Menu ▾ ▴

#2995 [FR] Per-sequence Two-Channel Auto-Type Obfuscation

KeePass_2.x
closed
nobody
None
5
2026-09-24
2026-09-24
No

Currently, Two-Channel Auto-Type Obfuscation can only be enabled or disabled for the entire entry.

It would be useful to allow disabling it for individual Auto-Type sequences. In some cases, username, password, etc. work correctly with obfuscation enabled, but TOTP or PIN input fails because the website displays the input as pop-ups and expects the digits to be entered in their original order.

The current workaround is to disable Two-Channel Auto-Type Obfuscation for the entire entry, which unnecessarily removes obfuscation from the other fields.

Possible implementations:

1) Add an option in the Auto-Type sequence editor to disable Two-Channel Auto-Type Obfuscation for that sequence.
2) Add a placeholder that disables Two-Channel Auto-Type Obfuscation for the sequence.

This would allow users to keep obfuscation enabled where it works while disabling it only for sequences that require strictly ordered digit input.

Discussion

  • Dominik Reichl

    Dominik Reichl - 2026-09-24
    • status: open --> closed
    • Group: KeePass --> KeePass_2.x
     

Log in to post a comment.