On 23/08/16 10:46, Karol Babioch wrote:
> However, it is annoying to be prompted for passphrases for each key in
> the keyring. This is even true for cases in which the public key of my
> smartcard is the first and only entry in authorized_keys on a SSH server.
Hm. I use both a smartcard and a
Hi,
Am 23.08.2016 um 10:36 schrieb Peter Lebbing:
> If I'm mistaken, I'd like to know. But I suspect the system was
> correctly designed to thwart such a thing.
I'm pretty sure you are right, so this is not my concern.
> So I don't think there is a need to ensure the correct key is used.
Howeve
On 23/08/16 10:20, Karol Babioch wrote:
> How are you guys dealing with multiple SSH keys while making sure the
> correct one is being used?
I don't make sure the correct one is used.
The challenge that is signed with your private key is based on data
provided by both the server and the client. I
Hi,
Am 21.08.2016 um 12:27 schrieb Peter Lebbing:
> Let me answer by example:
Thank you very much. I even knew about gpg-connect-agent, but didn't
connect the dots. I was too focussed on getting it to work through the
ssh-add interface. It does indeed work as outlined.
However it seems to be mor
On 21/08/16 00:11, Karol Babioch wrote:
> More specifically it seems to be impossible to delete identities from
> the agent once they are added.
Let me answer by example:
-8<--->8-
$ ssh-add -l
2048 27:f1:31:87:c8:05:5e:30:32:04:61:83:af:f5
Hi all,
I'm experimenting with using GPG as SSH agent. This basically works
fine, although I'm missing some advanced features, which the original
ssh-agent(1) provides.
More specifically it seems to be impossible to delete identities from
the agent once they are added. ssh-add -D returns: "All id
