https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #12 from Moritz Bunkus <mor...@bunkus.org> --- Sorry for spamming, but I think I should explain my use case here. I'm using ksshaskpass not just with ssh-add via SSH_ASKPASS, but also for other purposes, including: * letting mutt retrieve the password to my IMAP server login, * retrieving a password for the OpenConnect VPN client from the wallet, * automatically mounting encrypted file systems with encfs and its support for external password programs In each case I simply execute ksshaskpass with a custom prompt, e.g. "ksshaskpass 'IMAP password'". I've modified my scripts and configurations to adhere to ksshaskpass' new expectations; e.g. "ksshaskpass 'Enter passphrase for IMAP password: '", and that works for me. However, I'd rather this wouldn't be necessary, and that ksshaskpass would simply fall back to using the whole prompt as the storage key if the prompt wasn't recognized as one from ssh-add instead of refusing to work. Otherwise all use cases apart from ssh-add will run into this problem because they're not aware that the prompt must follow pattern (including the trailing colon and space — the RegExes are that strict!). -- You are receiving this mail because: You are watching all bug changes.
