SSH is the trouble-maker.
ssh has so many auth options: different port, username, key or password… one is wrong will make boringproxy unable to work.
Why not boringproxy itself do transport net packet? The client has linked to server, everything is ready.
Hi @xialvjun, the reason I used SSH initially is because I wanted to lean on existing tools. OpenSSH is proven and reliable. Overall I agree with you though. Good news is I’m currently working on a successor to boringproxy which solves these problems and others. Beta will hopefully be out in the near future.