An excruciatingly detailed guide to SSH (but only the things I find useful)
1–10 of 120 posts
Re: An excruciatingly detailed guide to SSH (but only the things I find useful)
#2Another member of the intergovernmental agency domain squatters club.
Re: An excruciatingly detailed guide to SSH (but only the things I find useful)
#3Great article that collected a lot of info that I usually wind up looking for separately.
But I have to ask: do people really find color schemes like this easier to read? I'm squinting at it throughout.
Re: An excruciatingly detailed guide to SSH (but only the things I find useful)
#4Another member of the intergovernmental agency domain squatters club.
For those wondering what this is referring to it's the use of ".int" for the TLD of the examples. ".test" and ".example" are the only really good reserved TLDs for this (".local" isn't quite what people think it is).
Re: An excruciatingly detailed guide to SSH (but only the things I find useful)
#5Great article that collected a lot of info that I usually wind up looking for separately. But I have to ask: do people really find color schemes like this easier to read? I'm squinting at it throughout.
[deleted]
Re: An excruciatingly detailed guide to SSH (but only the things I find useful)
#6Great article that collected a lot of info that I usually wind up looking for separately. But I have to ask: do people really find color schemes like this easier to read? I'm squinting at it throughout.
> do people really find color schemes like this easier to read
That scheme works great for me. Not just "dark mode," if it were my site i'd have made the colors more neon-ish.
Re: An excruciatingly detailed guide to SSH (but only the things I find useful)
#7Great article that collected a lot of info that I usually wind up looking for separately. But I have to ask: do people really find color schemes like this easier to read? I'm squinting at it throughout.
Do you mean the color scheme of the web page itself or the color scheme of the terminal in the screen captures? They're pretty close so maybe the distinction doesn't matter. The former seems more legible than most pages I see posted here since most of them have poor contrast. The latter is approximately what I use in my own terminal, except my text color is closer to that of the text editor screen capture than any of the shell ones for the same reason of contrast. I've pretty poor eyesight in general though so perhaps there's something to that.
Re: An excruciatingly detailed guide to SSH (but only the things I find useful)
#8Great article that collected a lot of info that I usually wind up looking for separately. But I have to ask: do people really find color schemes like this easier to read? I'm squinting at it throughout.
> do people really find color schemes like this easier to read That scheme works great for me. Not just "dark mode," if it were my site i'd have made the colors more neon-ish.
I find the color and the font hard to read... Guess we are all different.
Re: An excruciatingly detailed guide to SSH (but only the things I find useful)
#9For forwarding I almost never do -f. It can be a footgun in making it hard to tell which forwards are still open or operational.
-t is a cool trick, didn't know about that one.
An important note that's easy to overlook in the ~ escape command list is you can nest the escape when in nested sessions (i.e. if you're not using -J for whatever reason).
Cool list, it definitely lines up with what I've found useful and had a few more.
Re: An excruciatingly detailed guide to SSH (but only the things I find useful)
#10Another member of the intergovernmental agency domain squatters club.
For those wondering what this is referring to it's the use of ".int" for the TLD of the examples. ".test" and ".example" are the only really good reserved TLDs for this (".local" isn't quite what people think it is).
Example.com
People should just use example.com, it’s reserved and the most obvious to the end user that it’s for example purposes.