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

91–100 of 184 posts

Re: SSH Secret Menu

#91

Post by nh2 »

dnet wrote: post #72
vzaliva wrote: post #38

Earlier quoted context omitted.

It does not. open ssh linux to mac, typing ~ just types it on fish shell prompt. It works after`cat` followed by ENTER

In newer versions, it's disabled by default and you have to do something like this to enable in ~/.ssh/config: Host * EnableEscapeCommandline yes

`EnableEscapeCommandline` only controls the ~C commandline.

The reason that is disabled in current OpenSSH by default is OpenBSD `pledge` support:

https://security.stackexchange.com/questions/280793/what-att...

On my Linux,

    cat~.
closes the connection as expected, and no ~ is shown in the terminal.

Re: SSH Secret Menu

#92

Post by vlod »

0xbadcafebee wrote: post #3

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

I still struggle with the fact that I was (or delusional) an effective C programmer "back in the day" (before google etc) and all we had was "man" to look up std/x11 system calls.

Now I am dismayed with juniors who can't even be bothered to use google (or llms) to look up stuff on their first hiccup.

#include

Re: SSH Secret Menu

#93

Post by SEJeff »

AndrewDavis wrote: post #50
imwally wrote: post #23

Earlier quoted context omitted.

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

man -k, apropos, but less to type

Re: SSH Secret Menu

#94

Post by SEJeff »

vlod wrote: post #92
0xbadcafebee wrote: post #3

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

I still struggle with the fact that I was (or delusional) an effective C programmer "back in the day" (before google etc) and all we had was "man" to look up std/x11 system calls. Now I am dismayed with juniors who can't even be bothered to use google (or llms) to look up stuff on their first hiccup. #include

That’s not a builtin, so wouldn’t it be:

   #include

Re: SSH Secret Menu

#95

Post by gcr »

longislandguido wrote: post #49
0xbadcafebee wrote: post #3

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

Many Linux man pages have the thoroughness of a fortune cookie, so I can understand the skepticism. Jackpot if they're just a pointer to an 'info' page.

Most people just discount man pages as unreadable and don’t even try to understand them.

Case in point: the jq man page is incredible and everyone I know instead runs off to google or stackoverflow or Claude to answer simple questions

Re: SSH Secret Menu

#96

Post by obezyian »

SEJeff wrote: post #94
vlod wrote: post #92

Earlier quoted context omitted.

I still struggle with the fact that I was (or delusional) an effective C programmer "back in the day" (before google etc) and all we had was "man" to look up std/x11 system calls. Now I am dismayed with juniors who can't even be bothered to use google (or llms) to look up stuff on their first hiccup. #include

That’s not a builtin, so wouldn’t it be: #include

And it's kinda old, so maybe

  #define _POSIX_C_SOURCE 1
  #include

Re: SSH Secret Menu

#97

Post by sourcegrift »

jeremyscanvic wrote: post #86
halapro wrote: post #82

Earlier quoted context omitted.

I was never able to properly parse large man pages, I'm so happy that llms can now prepare half a usable command without spending an hour reading a time without a single usage example.

What I usually do when I have to read large man pages like bash(1) is I read them as PDFs: man -Tpdf bash | zathura - Replace zathura with any PDF viewer reading from stdin or just save the PDF. Hope that can be useful to someone!

my manpager is `vim -`, can't beat that

Re: SSH Secret Menu

#98

Post by bramgn »

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.

Be sure to hit enter before you start typing `~.`. It only works on a new line

Re: SSH Secret Menu

#99

Post by bell-cot »

bigstrat2003 wrote: post #25
blueflow wrote: post #2

As secret as the ssh manual.

"secret" not in the sense that it's hidden, but that most people won't know about it. Because approximately nobody actually reads man pages in their entirety, they just get in to find out how a specific flag works and then get out.

Using "secret" in that sense instantly reminds me of hyped-up headlines for time-waster news stories. Most people don't know what 2^8 is, either.

Re: SSH Secret Menu

#100

Post by aragilar »

bandie91 wrote: post #85
computerfriend wrote: post #83

Earlier quoted context omitted.

The drawback is that if you think your session is hanging and want to bail with ~., you have to press enter, which might actually make it to the server and execute something.

many get used to Ctrl-U, Return, ~, period keystroke sequence for this.

For those of us in today's 10000, Ctrl-U is the default readline shortcut for unix-line-discard (see https://www.gnu.org/software/bash/manual/html_node/Commands-... and https://susam.net/unix-line-discard.html).
Post reply on HN