Occurs when you create or import a new on-disk ssh key. The passphrase for the key is never accepted. Upstream is notified [1] and has confirmed the bug [2]. A patch to fix the issue is also already available [3]. I tried it in my local overlay and it fixes the issue on my system (~amd64, but I don't think that matters here). [1]https://bugs.g10code.com/gnupg/issue1184 [2]http://lists.gnupg.org/pipermail/gnupg-users/2010-January/038045.html [3]ftp://ftp.gnupg.org/gcrypt/gnupg/patches/gnupg-2.0.14-encode-s2k.patch Reproducible: Always Steps to Reproduce:
gnupg-2.0.15 has hit the tree and includes this fix
