SSH Secret Menu

Posted by piccirello 21 hours ago

Counter30Comment16OpenOriginal

https://xcancel.com/rebane2001/status/2031037389347406054

Comments

Comment by 0xbadcafebee 1 hour ago

Find the HIDDEN SECRETS that THEY DON'T WANT YOU TO KNOW!

    $ man ssh

Comment by bravetraveler 5 minutes ago

$LLM said... [unverifiable bullshit]

Comment by smoyer 31 minutes ago

HN as a tabloid ... After all enquiring minds want to know!

Comment by senectus1 22 minutes ago

hahaha made me laugh, thanks :-D

Comment by blueflow 1 hour ago

As secret as the ssh manual.

Comment by _kst_ 59 minutes ago

That doesn't do much good if you set `EscapeChar` to `none` in `.ssh/config`.

I find it convenient not to have to worry about accidentally entering escape characters. YMMV.

Comment by MayeulC 44 minutes ago

Note that it only works after pressing enter, so the odds are slim. In practice, I don't think I ever hit it by accident.

Comment by greyface- 2 minutes ago

I have noticed it while running ~/bin/some_command. The ~ doesn't echo until I also type the /. It doesn't cause any misbehavior because there is no binding for ~/ but can be slightly surprising.

Comment by wolvoleo 43 minutes ago

SSH does it pretty well though. Never once have I done it by mistake.

Comment by piccirello 56 minutes ago

I've been using SSH for ~15 years and never knew about these escape sequences. I'm eagerly awaiting my next hung session so that I can test `~.`. It's much nicer than my current approach of having to close that terminal window.

Comment by lathiat 40 minutes ago

Have been using that weekly since probably 20 years. Will change your life :)

My other favourite is I very often SSH with -v to figure out why the connection is hanging, you rapidly figure out if DNS is failing, the TCP connection doesn't open, it does open but no traffic flows at all or it opens and SSH negotiation starts but never finishes. You can learn a lot just from this about what is wrong.

Comment by sirfz 35 minutes ago

You can even chain them if you have deep ssh connections (i.e. ssh from one instance to another). I think it would be ~~. to terminate the 2nd hop.

Edit: it's already explained in the OP

Comment by wolvoleo 45 minutes ago

I use that every day but it's the only one I know by heart lol

Comment by shmerl 51 minutes ago

I've been using ~. on hung ssh connections for a while.

Comment by pram 1 hour ago

Yep the menu is handy for ssh tunneling. Maybe not a lot of people doing that these days though with stuff like dev tunnels and Tailscale.

Comment by MayeulC 37 minutes ago

I typically just create a "new" connection in a separate tab when I want to add tunneling.

I put new in quotes because I use another little-known feature, "ControlMaster". Multiplexes multiple connections into one, it makes making " new" sessions instant (can also be configured to persist a bit after disconnecting). Also useful for tab-completing remote paths. It does not prompt for authentication again, though. And it's a bit annoying when the connection hands (can be solved with ssh -o close, IIRC).