Bug#846175: [pkg-gnupg-maint] Bug#846175: gnupg-agent: Cannot use/delete ssh keys w/ empty passphrase

2016-11-29 Thread Werner Koch
On Tue, 29 Nov 2016 14:49, matth...@urlichs.de said: > When in doubt, do both? No. As I explained the key might be in use by other tools not just ssh. Tracking which key has been ssh-add'ed which has been taken from a different source would be pretty complicated. > In any case, if it's been

Bug#846175: [pkg-gnupg-maint] Bug#846175: gnupg-agent: Cannot use/delete ssh keys w/ empty passphrase

2016-11-29 Thread Matthias Urlichs
On 29.11.2016 10:39, Werner Koch wrote: > /* FIXME: What to do here - forgetting the passphrase or deleting > the key from key cache? */ > > Given that there is no easy way to know the origin of the key (it may > have been added by ssh-add or be for example a gpg subkey) I tend to >

Bug#846175: [pkg-gnupg-maint] Bug#846175: gnupg-agent: Cannot use/delete ssh keys w/ empty passphrase

2016-11-29 Thread Werner Koch
On Tue, 29 Nov 2016 00:20, matth...@urlichs.de said: > I can't delete them; "ssh-add -d path/to/file-pub" silently fails. > So does "ssh-add -D". gpg-agent does not support this because it stores the key in its own database. As you may have noticed ss-add is only required once to tell gpg-agent