102
submitted 1 year ago* (last edited 1 year ago) by starman@programming.dev to c/programming@programming.dev

The SSH port is 22. This is the story of how it got that port number. And practical configuration instructions.

top 12 comments
sorted by: hot top controversial new old
[-] teft@lemmy.world 49 points 1 year ago

The story is he asked IANA for port 22. They gave him port 22.

Why did this need to be a blog post?

[-] LastYearsPumpkin@feddit.ch 41 points 1 year ago

It's an interesting story anyway, kind of fun how the early days of the internet people just decided to build stuff and that random little tool from decades ago continue to be the backbone of much of the world. Imagine if all that stuff was proprietary...

[-] Rhaedas@kbin.social 9 points 1 year ago

True of many things we take for granted now. It would be a different world entirely. Another non-computer example would be the 3-point seat belt that Volvo left as an open patent, saving countless lives over the past decades.

[-] abbadon420@lemm.ee 21 points 1 year ago

This could've been an email

[-] starman@programming.dev 10 points 1 year ago

It also explains why it's 22

[-] LinearArray@programming.dev 2 points 1 year ago

The story is interesting though.

[-] Opafi@feddit.de 4 points 1 year ago

What part of the story are you referring to? The part where he asked for port 22 or the part where he got it?

[-] eager_eagle@lemmy.world 42 points 1 year ago

Anyway, I designed SSH to replace both telnet (port 23) and ftp (port 21). Port 22 was free. It was conveniently between the ports for telnet and ftp.

[-] roadrunner_ex@lemmy.ca 17 points 1 year ago

What a strange article. The reasoning for why 22 is interesting though very straightforward, and the rest of the article is essentially “I asked for port 22, and they gave it to me”. Little fanfare, little in way of storytelling conflict.

Not an issue in and of itself, but strange with a title of the form “This is the story of…” That sort of titling usually begets intrigue and triumph over adversity, dunnit?

[-] Opafi@feddit.de 9 points 1 year ago
[-] nanook@friendica.eskimo.com 5 points 1 year ago

Actually, I have my public facing servers configured to listen to 443 as well. Why? Because many corporate and public space wifi spots like libraries, will block 22, but allow 443 for https, so on my shell servers, I also listen to 443.

[-] Treczoks@lemm.ee 5 points 1 year ago

Back then, the internet was a thing of trust and cooperation. We got an assigned port number the same way. Current problem: Our company changed over the decades, and I no longer have the email address that would identify me to the IANA as the one who requested that number reservation.

this post was submitted on 12 Feb 2024
102 points (95.5% liked)

Programming

21847 readers
313 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS