@mjg59@nondeterministic.computer
Post #3652088
2026-07-07 07:08 UTC
Can anyone think why it would be a bad reason for ssh-agent to support being configured to pass specific extensions off to something else that speaks the SSH agent protocol, making it possible to implement custom extensions without needing to either upstream them or front the upstream SSH agent? (cc: @damienmiller@hachyderm.io I guess)
Replies (1)
-
@mjg59@nondeterministic.computer 2026-07-07 07:10
The context for this being hard at the moment is upstream's ssh-agent doesn't provide a way to implement custom extensions other than forking the agent. That's a huge pain, so the easy solution is to write your own entire agent and then have ssh talk to that, and your agent opens a connection to the upstream agent and sends those requests there. This is (a) tedious and (b) becomes amazingly complicated if you have more than one agent implementing a custom extension