haram
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
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Sounds legit. I feel I've done more abusive things with filesystems, though mostly 9p2000 :).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
...or a library you LD_PRELOAD that intercepts open() and redirects it to the real socket.
-
You mean connect(). It's a socket.
- Show replies
New conversation -
-
-
Does SSH open the connection before it does the agent request? You could potentially get SO_PEERCRED and netstat the connection endpoint
But that wouldn't allow nice handling of proxies or good jailing of the agent. -
My previous idea was to ProxyCommand something they told the agent what you're connecting to, but that has race condition issues with multiple connections
- Show replies
New conversation -
-
-
Done that with SSH keys before AuthorizedKeysCommand was a thing. Am I bad for thinking this isn't a that bad solution for extracting something there is no API for?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
What is the impetus before d this idea? What behavior are you trying to change and why are you trying to do so?
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.