Bug 4534 - Support authentication using public key held in ssh-agent
Summary: Support authentication using public key held in ssh-agent
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Bugzilla mail exporter
: 8233 (view as bug list)
Depends on:
Blocks: 7896
  Show dependency treegraph
Reported: 2013-02-06 10:48 CET by Peter Åstrand
Modified: 2024-02-06 09:23 CET (History)
3 users (show)

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2013-02-06 10:48:18 CET
This bug is similar to bug 4436. When using public key authentication, it would be nice if we could use keys held in a running ssh-agent. As far as I can tell, this does not work, since we are clearing SSH_AUTH_SOCK regardless of authentication type.
Comment 9 Aaron Sowry cendio 2023-09-07 11:04:47 CEST
Another benefit of this would be the ability to use GPG sub-keys to authenticate with ThinLinc via gpg-agent. gpg-agent supports ssh-agent emulation, so in theory we should get this feature "on the house".

Extracting a GPG sub-key in SSH format is non-trivial these days, so those who use gpg-agent for SSH authentication will have a hard time using the same key with ThinLinc.
Comment 10 Pierre Ossman cendio 2023-09-26 15:42:44 CEST
*** Bug 8233 has been marked as a duplicate of this bug. ***
Comment 11 Pierre Ossman cendio 2024-02-06 09:22:58 CET
macOS apparently has the weird setup where the key is still stored on disk, but the passphrase for it is stored in the keychain:


I am not sure if that's within scope here or not.

Note You need to log in before you can comment on or make changes to this bug.