The Untold Story of SSH

Comments · 148

• CO

  @CodeSource · 2 months ago · pinned

  Try Skywork Design → <a href="https://skywork.ai/p/1lf9Ly">https://skywork.ai/p/1lf9Ly</a><br><br>Turn ideas, PRDs, or screenshots into polished UI prototypes — export to Figma or HTML.<br><br>Code: codesource20 for 20% off annual

  17

• GA

  @Garance-Dro7 · 2 months ago

  I was one of the open-source developers who sent a few minor bug fixes to the original version of SSH. &nbsp;Nothing dramatic, just a few 2-5 line fixes sent in the late 1990&apos;s. &nbsp;I was quite upset when Tatu took the updates I sent to him, added those few lines of <b>mine</b> to a few source-files in SSH, and used those new lines to change the copyright of those files. &nbsp;It wouldn&apos;t surprise me if there were several developers in the world of OpenBSD which made the same kind of contributions <i>(and probably much more significant changes than mine!),</i> only to see <b>their</b> work used to justify changing the copyright. &nbsp;So for me it was not a surprise when OpenSSH was announced. &nbsp;I immediately contributed to it, although all I sent was probably $25 and I purchased a few T-shirts. &nbsp;I still have some of those OpenSSH T-shirts.<br>In my opinion it&apos;s a bit misleading to say the few significant bugs which can up in the ssh-protocols &quot;should have killed it&quot;. &nbsp;We (as an industry) cannot just abandon ssh <b>unless</b> there is something available which is better than it, and which is available on all the platforms that OpenSSH is already available on. &nbsp;That would be a pretty major task.

  383

• MK

  @mk-Denver · 2 months ago

  &quot;the connection for now will be secure&quot; &nbsp;that was a hard one🤫

  28

• RA

  @radiotec76 · 2 months ago

  I’ve been using ssh for 2 1/2 decades and it’s critical in my Ansible automation work. I did not know about the history of ssh and why it adopted port 22 until now. Thanks for the detailed history of this critical tool.

  74

• TH

  @ThisNameIsBanned · 2 months ago

  Thats what a Nobel-Prize really should go to, people that truly matter for EVERYONE.

  13

• AD

  @adrianswriting · 2 months ago

  It&apos;s worth noting that the NSA, GHCQ etc will always be happier if someone undoes a security patch and only they know about it, than having to go through all the effort of finding a new vulnerability.

  5

• PA

  @patrickwendo866 · 2 months ago

  You should cover sqlite next

  73

• TH

  @thepeterwan · 1 month ago

  I’m proud of having lived through those changes in my youth, back when OpenBSD was a real thing and a popular trend for building proxies and firewalls.

  2

• TE

  @Tee-w1d · 2 months ago

  I used to use rsh, rlogin, telnet and moved to to ssh for linux in early 2000&apos;s but still used rsh &amp; rlogin in solaris for a long time at my University network.

  7

• SY

  @syntaxerorr · 2 months ago

  The line every developer has used and non developers have never heard of it is something I think about a lot. And many other tools I use all the time. Wireshark, nmap, bash, git, etc.

  12

• RI

  @rikardottosson1272 · 2 months ago

  I mean, add a unit test that covers the bug, and then you won’t have regressions, but open SSL and open SSH aren’t known for stellar code quality or readability, with exploitable bugs existing for decades

  3

• BA

  @BabatundeTaiwo-e1l · 2 months ago

  I have been waiting all week. Thanks for all the good work

  10