I want to write an SSH agent that knows what user/host you're trying to connect to, but the protocol doesn't provide that. So I just had a ridiculous idea. What if I make a FUSE filesystem that materializes listening UNIX sockets on the fly, and set IdentityAgent to <fs>/%r@%h
-
...or a library you LD_PRELOAD that intercepts open() and redirects it to the real socket.
-
-
Indeed, that's what I meant, but remained stuck in the "filesystem" mindset.
-
If you want one agent per remote host, I think you can launch multiple ssh-agents with diffferent -a params and then in ssh_options map your ssh command to use one agent or another.
End of conversation
New conversation -
-
-
Yeah it's probably a btery idea to PRELOAD and override the socket than to write a FUSE program... However your fuse program would have a single application context if that's something you need for sharing info between sessions.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.