News for hackers. Stuff that matters.
Re:Sshmuxd: SSH proxy to replace jump hosts by dijit on Monday September 07, 2015 @04:27AM (#10180551)
I'm looking at the man page, I had no idea about `-W`. However, what does this protect against that the standard:

    ProxyCommand ssh -q <jumpHost> nc %h 22
doesn't protect?

Edit: just tried `-W` as an addition to the line but I get

   littlefish :: ~ » ssh pgsql3
   Bad stdio forwarding specification '<jumpHost>'
   ssh_exchange_identification: Connection closed by remote host
Re:Sshmuxd: SSH proxy to replace jump hosts by keeperofdakeys on Monday September 07, 2015 @05:32AM (#10180702)
Try formatting it like this:

    ProxyCommand ssh jumpHost -W %h:%p
-W is essentially the same as using nc, however it doesn't require executing a command on the jumphost. This project uses that fact to make the jumphost more secure (you can't execute arbitrary commands), and do destination white-listing for each user.
Re:Sshmuxd: SSH proxy to replace jump hosts by joushou on Monday September 07, 2015 @04:47AM (#10180592)
sshmux gives fine-grained user controls. In the normal jumphost example, you can use ssh -W to connect to arbitrary ports and hosts on the network, poking around where you weren't intended (ssh -W is just netcat where the ssh server initiates the connection for you). With sshmux, ssh -W will only work to hosts permitted for that user, and any other request will just fail.
Re:Sshmuxd: SSH proxy to replace jump hosts by zobzu on Saturday September 12, 2015 @06:50PM (#10209658)
-W is just a nicer wait of doing your nc command