GPG key to authenticate to SSH?

[Hauke Laging]

Am Mi 25.07.2012, 21:19:08 schrieb Werner Koch:

> With capability flags in private-keys-v1.d we could add a wildcard entry
> into sshcontrol and automagically use all keys flaged as "authenticate"
> or "use-for-ssh".  However, I am not sure whether this is a good idea,
> given that ssh iterates over all available keys and thus it may take
> some time to setup a conenction in case you have too many ssh capable
> keys available in gpg-agent.

Thus those few people who really have so many A-keys would simply not use this 
wildcard. Or they use both the wildcard and the current configuration so that 
they can tell gpg-agent which keys are the most often used so that these are 
tried first. Does gpg-agent currently care about the order of the entries?


Hauke
-- 
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 555 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20120725/0960dffd/attachment.pgp>