Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SSH Secret Menu

twitter.com

Post reply on HN
Print view View original

41–50 of 184 posts

Re: SSH Secret Menu

#41

Post by greyface- »

singlow wrote: post #31
greyface- wrote: post #17

Earlier quoted context omitted.

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.

I find it odd that you would have commands in ~/bin but not have it be the highest priority in your PATH. I use ~/.local/bin, but would never type it because i wouldn't have bins that overlap shell commands and no other path would have priority.

Usually, it is. IIRC, this was when I was just setting up my environment on a new host, after I had populated ~/bin but before I restarted my shell to pick up PATH modifications.

Re: SSH Secret Menu

#42

Post by krautsauer »

BenjiWiebe wrote: post #29
vzaliva wrote: post #26

I've used ~. for a long time but did not know about others. I know, should have read man page. Anyway, if you try it from shell prompt it is likely will not work as pressing ENTER shows the next prompt. Try `cat` followed by ENTER and then ~?

It'll still work. OpenSSH doesn't care about output (for ~ stuff), only input, so if you type ~. it will close the connection.

Does not for me, not even with busybox sh and no funky escape codes in PS1 at all. It does with cat or yes running, so just something being output is not the problem… Hm.

Re: SSH Secret Menu

#43

Post by olalonde »

Wow, never knew this... That said I'm not sure if I'll remember using it as my muscle memory is already trained to kill hung processes via ctrl-b s, ctrl-k, ctrl-b x (in tmux).

Re: SSH Secret Menu

#44

Post by snvzz »

tomxor wrote: post #22
piccirello wrote: post #6

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.

If hung SSH connections are common it's likely due to CGNAT which use aggressively low TCP timeouts. e.g. I've found all UK mobile carriers set their TCP timeout as low as 5 minutes. The "default" is supposed to be 2 hours, you could literally sleep your computer, zero packets, and an SSH connection would continue to work an hour later, and generally speaking this is still true unless CGNAT is in the way. If you are…

Note this is only an issue if not using IPv6.

CGNAT is for access to legacy IPv4 only.

Re: SSH Secret Menu

#45

Post by andrewflnr »

I've been using the ~. shortcut for a while, but somehow escaped learning about the help menu.

Another neat thing I noticed while playing with it just now: there's an option to enter ~ twice to send a literal ~, but usually you don't have to do this when typing something like 'ls ~' in a regular session. Not only does the ~ have to be the first character on a line to start an escape sequence, but typing on a line, backspacing all the way to the start and then typing ~ also sends a literal tilde. It only triggers the escape sequence if the ~ is the chronologically first character after a newline (or first in the session), which is an unlikely thing to type into a shell in a normal session. Good choice of UI, both the character and the state machine.

Re: SSH Secret Menu

#46

Post by ghrl »

MayeulC wrote: post #12
pram wrote: post #4

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.

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…

I'm using that as well but had issues with tunneling where it creates the tunnel in the background and terminates and so you might not know the random port it assigned or I couldn't figure out how to un-tunnel it and tunnel again to the same port. Just bypassed the control master then.

Re: SSH Secret Menu

#48

Post by NitpickLawyer »

MayeulC wrote: post #12
pram wrote: post #4

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.

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…

> I use another little-known feature, "ControlMaster". Multiplexes multiple connections into one, it makes making " new" sessions instant

Is this what secureCRT used as well? I remember this being all the rage back when I used windows, and it allowed this spawn new session by reusing the main one.

Re: SSH Secret Menu

#50

Post by AndrewDavis »

imwally wrote: post #23
0xbadcafebee wrote: post #3

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

I blew a few minds a week ago when I told my younger coworkers about man pages. I hit ‘em with the `man man` and one dude was like “whoa!”

Further blow their minds by showing them `apropos` https://manpages.debian.org/testing/man-db/apropos.1.en.html
Post reply on HN