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 about the key. The code to remove the indentity has this
comment:
/* 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
implement the latter (i.e. forgetting the passphrase).
> gpg-agent[6308]: failed to unprotect the secret key: No passphrase given
>
> Umm, yes a passphrase *was* asked for, and given; it just happens to be
> empty. So? This worked before updating my system to Testing yesterday.
Indeed there is a bug when adding an ssh-key w/o passphrase.
I filed gnupg bug
https://bugs.gnupg.org/gnupg/issue2856
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgp3fa97Zx9Jx.pgp
Description: PGP signature
