Timeline for SSH with ProxyCommand never connects
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 26, 2023 at 8:16 | comment | added | Ragesh |
@JaromandaX it looks like you were right. Even though nc on its own works, when it's being called by ssh, it immediately sends a version string which confuses the heck out of mitmproxy. I naively assumed that the CONNECT tunneling would allow this to work but it looks like it needs more work. Thanks for the pointer!
|
|
| Jul 26, 2023 at 8:14 | answer | added | Ragesh | timeline score: 0 | |
| Jul 26, 2023 at 6:50 | history | edited | Ragesh | CC BY-SA 4.0 |
added 616 characters in body
|
| Jul 26, 2023 at 6:48 | comment | added | Ragesh |
man ssh_config also says "This (the ProxyCommand) directive is useful in conjunction with nc(1) and its proxy support. For example, the following directive would connect via an HTTP proxy at 192.0.2.0". I've tried the same nc command from there and still no connection.
|
|
| Jul 26, 2023 at 6:22 | comment | added | Ragesh | That is true; I am just trying a few things to validate some ideas. I assumed it would at least try to connect with the tunnel. It is executing the ProxyCommand (I can see it in htop), but no actual connection happens. I am not sure what is blocking it when it is being executed by ssh. Directly running the command shows me a TCP tunnel being opened in mitmproxy. | |
| Jul 26, 2023 at 6:13 | comment | added | Jaromanda X |
is there any guides to using mitproxy for SSH on the mitproxy site? looks like mitmproxy is for http, websockets etc, not for SSH which is a completely different protocol to the former
|
|
| S Jul 26, 2023 at 6:07 | review | First questions | |||
| Jul 26, 2023 at 8:15 | |||||
| S Jul 26, 2023 at 6:07 | history | asked | Ragesh | CC BY-SA 4.0 |