Live data from Hacker News

How SSH Port Became 22

ssh.com

61–70 of 89 posts

Re: How SSH Port Became 22

#61

This makes me wonder. What such booming technology is there right now where I can contribute something like this and make a mark for myself? Having born much later in the history of Internet, I think I have missed out on many of the early magical years of the Internet. But if I can get involved in some other technology that is in early stage and booming and where I have a chance to contribute something that may becom…

The most unsatisfying but realistic answer is probably that you're best off working on whatever sparks your passion, because making dent in the universe seldomly happens intentionally, and if you don't succeed hugely at least you had fun and learned a lot on the way.

If we're talking about basic tech such as networking, the time for foundational work has probably passed, or it has at least become exponentially more unlikely that you'll contribute another bedrock protocol or mechanism. It's also worth noting that you never hear from the many thousands of technologies that either failed to reach critical mass or became obsolete a long time ago. Just like founding a startup, this will be the most likely outcome.

If you're looking to be the first to do something, my advice is: try to do it in space. Seriously. Finally things are happening again there, and you can probably make your mark inventing basic necessities and/or being one of the first people to colonize a new place.

If you're looking for something in software, opinions on what's needed differ a lot. As an old person, my perspective is that we're going to need a way to deal with complexity and brittleness. Our software stacks have become bloated, unreliable, and a nightmare to debug. Things are getting slower and more buggy year by year, because we have not yet hit the right balance between using low-level primitives and high-level abstractions. We're now using huge frameworks regularly for very simple things, both because it's what we're used to and because these frameworks help paper over design defects lower down the stack. This needs to be solved, we can't keep stacking things on top forever. There is a real, concrete danger to our society here.

Re: How SSH Port Became 22

#62

This makes me wonder. What such booming technology is there right now where I can contribute something like this and make a mark for myself? Having born much later in the history of Internet, I think I have missed out on many of the early magical years of the Internet. But if I can get involved in some other technology that is in early stage and booming and where I have a chance to contribute something that may becom…

Unreal Engine. Its the next OS.

Re: How SSH Port Became 22

#63
slightly offtopic: I wish scp also used -p instead of -P for defining a custom port, everytime I want to ssh or scp on a custom port I have to look up which one of the two uses -p or -P :)

Re: How SSH Port Became 22

#64
post #58

Funnily enough, changing the ssh port to a random unprivileged one is now possibly the easiest and most effective step to harden a box... I guess it shows how the internet has changed.

In the last two months, I've been getting lots of bruteforce scan attempts on all my boxes that run ssh on high ports, so it seems this is no longer as effective as it was :-/

Re: How SSH Port Became 22

#65
post #13

Personally I find how/why FTP uses two ports, 20 and 21, to be more interesting: So the first thing to know is the FTP is 'old', in that it predates TCP and originally ran on NCP: > The original specification for the File Transfer Protocol was written by Abhay Bhushan and published as RFC 114 on 16 April 1971. Until 1980, FTP ran on NCP, the predecessor of TCP/IP.[2] The protocol was later replaced by a TCP/IP versio…

Also, Telnet was originally port 1 and FTP was port 3 (RFC 433, December 1972). On an incompatible protocol change (mentioned in RFC 542, August 1973), they were "temporarily" moved to 23 and 21 respectively until the old versions were taken down. Of course, the move back to 1 and 3 never happened. Wouldn't FTP need three simplex connections - commands to server, responses from server, data transfer?

And till fairly recently a gotcha for firewalls and when the firewall team is different from the requesting team oh the jokes

Re: How SSH Port Became 22

#66

Earlier quoted context omitted.

"Hei" means "hi". You can use that in your email. English "hey" is said when someone is annoyed. "Hey you! Stop that!"

Hmm, tone is what differentiates the greeting and the admonishment. Your 2nd sentence is correct, but not exclusively. TL;DR I use "hey" as a greeting. [en-gb native]

> "hey" as a greeting

I blame the US TV series "Friends" for that.

Curiously the OED doesn't (yet) have this greeting sense.

Re: How SSH Port Became 22

#67

Earlier quoted context omitted.

"Hei" means "hi". You can use that in your email. English "hey" is said when someone is annoyed. "Hey you! Stop that!"

Hmm, tone is what differentiates the greeting and the admonishment. Your 2nd sentence is correct, but not exclusively. TL;DR I use "hey" as a greeting. [en-gb native]

But it's very informal/slang, used among peers. e.g. If I answered the phone to an unknown caller I'd say 'Hello?', but a friend might get a 'Hey.'

I certainly wouldn't say 'Hey IANA, please reserve me port 22' any more than I would sign off 'kthxbye'.

[also en-gb native]

Re: How SSH Port Became 22

#68
post #66

Earlier quoted context omitted.

Hmm, tone is what differentiates the greeting and the admonishment. Your 2nd sentence is correct, but not exclusively. TL;DR I use "hey" as a greeting. [en-gb native]

> "hey" as a greeting I blame the US TV series "Friends" for that. Curiously the OED doesn't (yet) have this greeting sense.

> Curiously the OED doesn't (yet) have this greeting sense.

Interesting, neither does my (more liberally accepting than Oxford) 2016 Collins. I've certainly been using it as an informal greeting since '00s.

I don't know if I got it from Friends, it wouldn't have occurred to me, but I did start watching it around that time so it's certainly plausible.

Re: How SSH Port Became 22

#69
post #59
post #51

Reminds me of a story about a professor. He has framed an old request for a grant and put it up in his office: > I need 20000US$. That's all it reads (with value converted to today's dollar-value for easier interpretation) - and of course it was granted.

I'd love to get a little more context. Who applied for the grant? Where was this?

https://dirnagl.com/2014/01/14/otto-warburgs-research-grant/

Re: How SSH Port Became 22

#70
post #36

Earlier quoted context omitted.

Most of us rarely write such formal letters. I don't remember when is the last time I've written something as formal for a Finnish recipient. At school I was taught to use "Dear Sir or Madam" or "To whom it may concern" but neither of those sound natural, they're just learned. If writing for a Finn, I just start with "Hei" ("Hey") (in fact that has lead me to start emails in English with just "Hey" as well). I may ha…

"Hei" means "hi". You can use that in your email. English "hey" is said when someone is annoyed. "Hey you! Stop that!"

[deleted]
Post reply on HN