(I have read about the risk of ssh agent forwarding and am only using
it in limited circumstances, mainly to do `git pull` on a server.)
adam@laptop $ ssh-add -l
# lists currently unlocked keys correctly
adam@laptop $ ssh -A remote0
# login messages
adam@remote0 $ ssh-add -l
# lists currently unlocked keys correctly
adam@remote0 $ exit
# logout messages
adam@laptop $ ssh -A remote1
# login messages
adam@remote1 $ ssh-add -l
Could not open a connection to your authentication agent.
Do I need to enable something in my configuration on remote1 to make
it work?
Do I need to enable something in my configuration on remote1 to make
it work?
On 1/27/22 5:02 AM, Adam Funk wrote:
Do I need to enable something in my configuration on remote1 to make
it work?
The "AllowAgentForwarding" configuration parameter for the sshd daemon
can interfere with / prohibit clients forwarding agents to a server.
For completeness, in case someone else has a problem that isn't related
to shared connections.
That's interesting and useful to remember
(although it didn't apply in my case)
thanks!
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 491 |
Nodes: | 16 (3 / 13) |
Uptime: | 101:25:17 |
Calls: | 9,682 |
Calls today: | 3 |
Files: | 13,725 |
Messages: | 6,174,908 |