6 ms·
It's not a terribly interesting story IMO. The author (Tatu Ylonen) sent an email to Joyce K. Reynolds at IANA, on release of v.1.0 of SSH protocol, and IANA a
by pbhjpbhj 10y ago
It's not a terribly interesting story IMO.
The author (Tatu Ylonen) sent an email to Joyce K. Reynolds at IANA, on release of v.1.0 of SSH protocol, and IANA agreed to assign port 22.
That's kinda it.
A summary of SSH use follows the story which is a good overview for someone new to it.
- beaconstudios 10y agoI think it's interesting for how simple and informal it was in 1995. I always imagined that port allocation was a much more formal process more akin to an ISO or ECMA standardisation, but nope - Tatu sent an email asking for it and Joyce basically just replied with "sure thing, it's yours". For something as critical as port allocation it's pretty interesting/funny how casual it was.
- zb 10y agoThe process hasn't really changed much (I applied for a port allocation 5 years or so ago). There's a little questionnaire you fill out, and there might be some back-and-forth over email to clarify the answers but basically it's no more complicated than you email someone and if you fit the criteria they reply with your port allocation. What has changed is that there is essentially no chance of getting a privileged port allocated now.
- hirsin 10y agoYep it's still very easy and informal. I did it a year or two back to get a DNS-SD entry [1] defined. Just fill out the form [2] and do some back and forth - even updating it is easy. Also yes, a dedicated port is very hard to get - you thought IPv4 was running out ;) One of the side effects of them being such a widespread and networked group is that when I made my application, they suggested I go talk to one of my coworkers (as loosely defined as that is at Microsoft) since he helped standardize the body anyhow. A bit of zen - "the answers you seek were within you[r org chart] the whole time" 1. https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=wdp https://www.iana.org/assignments/service-names-port-numbers/... 2. https://www.iana.org/form/ports-services https://www.iana.org/form/ports-services
- antocv 10y agoCritical how? Its just an informal agreement. Its just a 16bit number.
- beaconstudios 10y agocritical in the sense of avoiding collisions between protocols. Imagine if redis and mysql had ended up with the same default port, and how much of a nightmare that would be.
- ams6110 10y agoIt would only mean you could not run redis and mysql on the same host, and your default assumption about what port to connect to might be wrong 50% of the time. Easily handled, though. There are certainly cases of different software using the same unprivileged ports by default. It's probably more rare for the privileged ports.
- antocv 10y agoWho runs redis and mysql on public facing ports? Whats the big deal if you run ssh on port 443 as many do, together with nginx on the same port? Or if you run a web-server on port 22 and irc on 21.
- coldtea 10y ago>Whats the big deal if you run ssh on port 443 as many do, together with nginx on the same port? The deal is that if we're talking of TPC apps on a single network interface, you can't. The deal is also that it's handy to know where you can expect to see a common service running.
- icebraining 10y agoThe deal is that if we're talking of TPC apps on a single network interface, you can't. No, but you can fake it with sslh: http://www.rutschle.net/tech/sslh.shtml http://www.rutschle.net/tech/sslh.shtml
- macintux 10y agoReminds me a bit of how Eli Lilly landed a class A subnet. They applied for a class B sometime around 1990, but Postel found out how large their company was and gave them an A instead. (Update: s/network/company/ I doubt they had all that many networked computers at the time, but fuzzy memories of a third-hand story.)
- hughw 10y agoHalliburton (34.0.0.0) and Ford (19.0.0.0) too.
- TorKlingberg 10y agoHE sort of should have realized there aren't enough class A:s even for companies of Eli Lilly's size.
- devdas 10y agoIPv4 was an experimental protocol. http://dltj.org/article/vint-cerf-ip-addressing/ http://dltj.org/article/vint-cerf-ip-addressing/
- i336_ 10y agoHah. Just like sockets were a "okay we'll just use this hack until we come up with something better." I think sockets (or what became sockets) crystallized (or started that process) around MULTICS?
- macintux 10y agoHe apparently later lamented that Lilly wouldn't return it. I believe they've released large chunks of it by now.
- gist 10y agoRFC's were informal. Kind of like 'Sup, here is my proposal for...' https://en.wikipedia.org/wiki/Request_for_Comments https://en.wikipedia.org/wiki/Request_for_Comments "Unlike the modern RFCs, many of the early RFCs were actual requests for comments and were titled as such to avoid sounding too declarative and to encourage discussion"
- forgotpwtomain 10y agoMeanwhile Author's found that very few people were commenting on them, and decided that they might as well declare and standardize from the get go ;)
- nasalgoat 10y agoWhen I registered my first .com address in 1995, I emailed "the guy" who handled them after getting the NCSA webserver up so they could prove I had a server. Things were considerably more casual in the 90s...
- beaconstudios 10y agoI hope you got a good one!
- deleted 10y ago[deleted]
- endorphone 10y agoIt's interesting to me simply because it's so profoundly critical, moving the platform dramatically ahead (and serving as the basis of so many other systems), and somehow it was never humanized to me -- it just was. Seeing the author discuss their motivations and process is fascinating to me.
- rocky1138 10y agoIt's also interesting because he wrote an email to just one person and it took no other real effort to make such a huge sweeping change to the Internet. I wonder if the creator of ssh thought that he/she would still be working on it in 2017.
- finid 10y agoIt might not seem much to you now, but to a student in Finland, receiving an immediate and positive response to a request from a very important person in your field is y(h)uge. I recall the feeling I got the first time I sent a message to the Nessus mailing list. I couldn't compile the program so I was asking for help. I thought I was going to wait for a long time, but was surprised when a response came a few minutes after. The response came from the author of the program itself, and he was very nice in how he answered my question. It was obvious that I was a noob and needed hand-holding. It made a lot of difference to me. You have no idea how that positive response affected Tatu. Edit: Changed possible to positive in the last paragraph.
- atsaloli 10y ago@finid's post reminded me of when I asked for help on the CFEngine mailing list and got prompt and kind response from the author; who even advanced the release schedule to meet my needs. This was while the author (unbeknownst to me) was putting together a company, dealing with VC's, etc. I blogged about this at http://verticalsysadmin.com/blog/cfengine-is-awesome/ http://verticalsysadmin.com/blog/cfengine-is-awesome/
- coldtea 10y ago>It's not a terribly interesting story IMO. You'd be surprised in how interesting me and other find this story. Of course if you grew up talking all these for granted, and don't have an interest at how things were back then, it might not be. But there are tons of interesting stuff in this short post, including the informality of how SSH started.
- pbhjpbhj 10y ago>if you grew up [taking] all these for granted, and don't have an interest at how things were back then // Bit pejorative there. I find it more "huh, nice to know" rather than "wow, I'll tell my friends"; I'll hand in my rainbow books on the way out ...
- andirk 10y agoIf I showed you the email asking that the "go" light be green, and the people who control vehicle traffic on the entire earth were like "ok green it is", would that be interesting to you?
- pbhjpbhj 10y agoI'm not really in to artefacts in that way. Somebody decided to use green, there might even have been a letter sent, but it's an expected part of creation of a traffic light colour; so no i would really find that of particular interest. (BTW it seems green was used in analogue to train signals, early traffic signals use semaphores, like train signals, which go back to use of signal flags). I've been using the internet since one could decide how to route the emails one sends, I've used SSH a lot: it's just not interesting as a story, it's barely a factoid. FWIW I think a better analogy is the adoption of CQD as the distress signal for Morse operators (https://en.m.wikipedia.org/wiki/CQD https://en.m.wikipedia.org/wiki/CQD). It's interesting, but the manner in which it was adopted has no story to it.
- lowlevel 10y agoI had always just assumed 22 was picked because it was next to telnet/23. Seems like an obvious choice anyway... I guess it being just a single query to the IANA and a single response to make it official is surprising.
- jpalomaki 10y agoAnd the whole thing was resolved within the same day: Request: Mon Jul 10 11:45:48 +0300 1995 Response: Date: Mon, 10 Jul 1995 15:35:33 -0700
- interfixus 10y agoIt's a great little story, shining a nostalgic light on the simplicity of life, the universe etc. in 1995.
- wand3r 10y agoThat's precisely what makes it interesting. It was a remarkably simple interaction for something many consider to be a critical service. What if they simply said; no. Try again in a year. I wonder if SSH would be widespread today if that were the case