Forgot your password?
typodupeerror
Encryption Announcements Privacy Security

OpenSSH Going Strong After 10 Years With Release of v5.3 249

Posted by timothy
from the can't-even-speak-plainly dept.
An anonymous reader writes "OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. It encrypts all traffic (including passwords) to effectively eliminate eavesdropping, connection hijacking, and other attacks. Additionally, OpenSSH provides secure tunneling capabilities and several authentication methods, and supports all SSH protocol versions. Version 5.3 marks the 10th anniversary of the OpenSSH project."
This discussion has been archived. No new comments can be posted.

OpenSSH Going Strong After 10 Years With Release of v5.3

Comments Filter:
  • by 93 Escort Wagon (326346) on Thursday October 01, 2009 @10:27PM (#29613359)

    Thank you to everyone that's worked on OpenSSH over its lifetime - it's certainly made my (working) life easier.

    And, unlike the Slashdot submission system, OpenSSH pretty much always works!

  • by La Gris (531858) <lea@gris.noiraude@net> on Thursday October 01, 2009 @10:30PM (#29613379) Homepage

    This wonder-full versatile tool shaped the world of remote administration or the other way round.

    Would you ?

    1) Abandon SSH or OpenSSH
    2) Loose an arm
    3) I'm a snake
    4) Telnet everywhere
    5) I live in a data-center

  • And best of all... (Score:3, Insightful)

    by Timothy Brownawell (627747) <tbrownaw@prjek.net> on Thursday October 01, 2009 @10:32PM (#29613385) Homepage Journal
    ...it remembers what key goes with what server, rather than unconditionally giving each of a few dozen outside groups the ability to tell it that yes, your secure server really did just get a new key (so that new Russian IP address must be correct).
  • Thanks OpenBSD (Score:5, Insightful)

    by Spit (23158) on Thursday October 01, 2009 @10:38PM (#29613415)

    For the rest as well.

    • Re: (Score:3, Insightful)

      by atheistmonk (1268392)
      They really are a gift that keeps giving. I'm not really much of an OpenBSD user... I don't always like that Theo de Raadt assumes he knows what's best for me. Unfortunately... He's probably right. May it live forever and spawn more and more secure and useful tools for the F/OSS world.
      • Re:Thanks OpenBSD (Score:5, Interesting)

        by JackieBrown (987087) <dbroome@gmail.com> on Friday October 02, 2009 @12:18AM (#29613857)

        What is interesting is how secure and easy it is to use.

        I use it with fuse to mount my networked partitions. It involved no work and the fact that it is secure is just a bonus since there is no noticable speed loss for my transfers

      • Re:Thanks OpenBSD (Score:4, Insightful)

        by Anonymous Coward on Friday October 02, 2009 @01:34AM (#29614141)

        Theo de Raadt is not all powerful. The project is stagnating now in some areas in spite of him being the leader. However nobody can deny he and his team are some of the best programmers around.
        OpenBSD source code is the best I have ever seen and the first thing I do on any new Linux installation is to install OpenBSD tools.
        Really if someone is reading this and wants to flee the Linux gulag, OpenBSD is a system to check. It is not the fastest, it is not the smallest, but it is the most secure and consistent.

    • Re:Thanks OpenBSD (Score:4, Informative)

      by Dadoo (899435) on Friday October 02, 2009 @01:24AM (#29614097) Journal

      I'd like to thank the OpenBSD project, as well, but I'd also like to point out a few issues.

      OpenSSH still won't work with certificates signed by a CA.

      OpenSSH doesn't allow an unencrypted connection (after authentication). Not all CPUs can encrypt/decrypt at 1Gbps.

      OpenSSH doesn't work - as advertised - with an exclamation point in a "Match" statement.

      Other than that, OpenSSH is possibly one of the most capable and reliable pieces of software I've ever had the privilege to use.

      • Re: (Score:3, Informative)

        by Chris Pimlott (16212)

        OpenSSH doesn't allow an unencrypted connection (after authentication). Not all CPUs can encrypt/decrypt at 1Gbps.

        I believe there is a compile-time option to include a noop cipher as a run-time option, it's just not included by default.

        • Re: (Score:3, Insightful)

          That would make the connection unencrypted during the authentication, and would need to be manually enabled on all sites where you would use it. Not that it matters, it would be an anti-feature anyway.

      • Re: (Score:3, Informative)

        by gad_zuki! (70830)

        >Not all CPUs can encrypt/decrypt at 1Gbps.

        FTPS does this. You can disable/enable encryption on the fly. I believe this functionality is disable in filezilla by default, but other servers support it.

  • by stox (131684) on Thursday October 01, 2009 @10:38PM (#29613419) Homepage

    To think we used to use telnet and rlogin to access everything.

    OpenSSH is a far more significant technology than it has gotten credit for.

    • by the_humeister (922869) on Thursday October 01, 2009 @11:00PM (#29613515)

      Same with zippers. What would life be like without zippers?

    • Re: (Score:3, Insightful)

      by Anonymous Coward

      Except OpenSSH really shouldn't get the credit. Tatu Ylönen created ssh, not OpenBSD. The original OpenSSH implementation was based on Tatu's code. I'm not arguing that OpenSSH isn't useful, or that they haven't done good work, but it is not the origin of the technology.

      • by evilviper (135110) on Friday October 02, 2009 @12:53AM (#29613987) Journal

        The original OpenSSH implementation was based on Tatu's code.

        Yes it was. But Tatu's SSH was the old, insecure protocol.

        And there were many secure remote access tools before it. kerberized telnet, telnet/ftp over SSL, and limitless others.

        It's not the magical protocol (which is quite similar to SSL plus RSH/RCP), or the initial few lines of code that got it started. It's the fact that it was open, secure, widely available, and being pushed by the OpenSSH folks to be used as the default form of remote access on Unix systems.

        Tatu didn't have anything to do with it. He was too busy commercializing it, and repeatedly threatened, and then suing the OpenSSH project for all their hard work. If he had chosen to keep SSH open, we'd have been a LOT further along. As other posters correctly remember, support for SSH very nearly died with that step. Many programs included SSHv1 support, and then just stagnated and let the code rot. If not for OpenSSH, it would be another relic of secure telnet protocols tried and failed, not having gone anywhere, and we'd go merrily along, using telnet and rsh, bemoaning the fact that it's so insecure, and that nothing better ever came along.

        • by Anonymous Coward on Friday October 02, 2009 @04:26AM (#29614711)

          Version 2 of the SSH protocol was also developed by Tatu YlÃnen and his company SSH Communication Security. It was just that they when they made the new, improved protocol they also switched to a proprietary license with SSH v2. It took a couple of years before the OpenBSD folks had developed the open source SSH v1 code to the point where it supported all features of the SSH v2 protocol. The two implementations of v2 still aren't fully compatible on client-side stuff like key storage, but nowadays it is the proprietary SSH that is considered the odd one out.

          I don't consider Tatu YlÃnen here as a bad guy. What he has given to the world free of charge is 1) the SSH v1 protocol specification, 2) the SSH v1 open source implementation, and 3) the SSH v2 protocol specification. On top of that he has managed to make a living off of the SSH v2 code, and he certainly has the right to do that.

    • by mlts (1038732) *

      The only other protocol available at the time that might have even approached SSH would be a SSL based telnet. I'm not sure how rlogin would have been secured (because it is UDP based), but it likely would be nowhere near as elegant as what ssh offers.

      To boot, neither telnet or rlogin offered port forwarding (which meant an easy way to use X clients over an insecure network), variable security methods (so you wouldn't need to worry about a password, but could use a private .identity key), multiple encrypti

    • by Alioth (221270)

      Not only that, but telnet and rlogin over 10base2 thin-net or 10baseT with a hub rather than a switch, so anyone on your LAN segment could see your passwords going by...

  • by VonGuard (39260) on Thursday October 01, 2009 @10:40PM (#29613429) Homepage Journal

    No matter the OS, no matter the exploit, that name alone in the title of an email to bugtraq can send shivers down the spine.

  • by digitalsushi (137809) <slashdot@digitalsushi.com> on Thursday October 01, 2009 @10:45PM (#29613459) Journal

    i dont need ssh... for some reason inetd was installed with a call to bash, running as root. i can just telnet right in. it actually saves me a ton of time, since lately i can't even seem to remember what my password is.

  • No idea what I would do without it.

  • Did OpenSSH ever fix the performance limitation on fast networks (>100Mbps)? They have static internal flow buffers that prevent fast scp/ssh! HPN has a patch but OpenSSH has to my knowledge never adopted it. http://www.psc.edu/networking/projects/hpn-ssh/ [psc.edu]
    • by Techman83 (949264)
      I find I'm pushing Disk/CPU/Network rather then limitations with SCP. I figure the encryption is causing the CPU load, the rest is obvious.
    • by WuphonsReach (684551) on Friday October 02, 2009 @12:00AM (#29613801)
      Like the other poster, I've see 30-50 MB/s (300-500 Mbps) over a gigabit network when copying between boxes using scp. The limitations were more the frame size (not using jumbo frames on that network) along with the read/write speeds of the system on each end.

      So, it's no slouch and better then SMB/CIFS.
  • To the best (Score:4, Insightful)

    by Powys (1274816) on Thursday October 01, 2009 @11:06PM (#29613551)
    My hats off to probably the best open source package ever made
  • by Vellmont (569020) on Thursday October 01, 2009 @11:34PM (#29613687)

    It was likely not far after openSSH became available, and the original SSH was starting to get less and less friendly. The great thing about SSH is is all started out free and open. Early on it was experimental (though very cool). This later changed when the original SSH became commercialized, and the licensing started closing up (thus my switching to openSSH). This was back in the days when an ssh client was something you had to hunt around for and much of the time all that was available was cruddy ssh1 clients.

    We've come a long way since then. These days putty and SCP are available for any platform. I haven't even thought about the original ssh from Tatu for years, though I certainly used it so many years ago.

  • The openssh web page [openssh.com] says:

    Please take note of our Who uses it page, which list just some of the vendors who incorporate OpenSSH into their own products -- as a critically important security / access feature -- instead of writing their own SSH implementation or purchasing one from another vendor. This list specifically includes companies like Cisco, Juniper, Apple, Red Hat, and Novell; but probably includes almost all router, switch or unix-like operating system vendors. In the 10 years since the inception of the OpenSSH project, these companies have contributed not even a dime of thanks in support of the OpenSSH project (despite numerous requests).

    Not wanting to troll but, you know, if openssh was GPL licensed said commercial vendors would have to release the source for openssh with their products, including any modifications they made. The project could also offer LGPL or BSD licensed versions in exchange for cold, hard, cash.

    • Re: (Score:3, Insightful)

      by Yosho (135835)

      Not wanting to troll but, you know, if openssh was GPL licensed said commercial vendors would have to release the source for openssh with their products, including any modifications they made. The project could also offer LGPL or BSD licensed versions in exchange for cold, hard, cash.

      You're assuming that the commercial vendors would still use OpenSSH if it was GPLed. What makes you think they wouldn't either roll their own SSH server or use some other proprietary implementation?

      • Not wanting to troll but, you know, if openssh was GPL licensed said commercial vendors would have to release the source for openssh with their products, including any modifications they made. The project could also offer LGPL or BSD licensed versions in exchange for cold, hard, cash.

        You're assuming that the commercial vendors would still use OpenSSH if it was GPLed. What makes you think they wouldn't either roll their own SSH server or use some other proprietary implementation?

        It would come down to economics. Is an LGPL version of openssh cheaper than commercial implementation X? This approach works for adacore. [adacore.com]

        But for sure, fewer products would contain openssh if it was GPLed. But with more money it might be a better product, so there might be a net iimprovement in security that way.

        • Throwing money at security won't make something more secure. That's really up to who is doing the programming i.e. how competent they are. Just look at all the security products out there that have massive security holes in them regardless of whether they are commercial or open-source.

    • Re:License (Score:4, Insightful)

      by Secret Rabbit (914973) on Friday October 02, 2009 @01:21AM (#29614081) Journal

      I do believe that you've entirely missed the point of that paragraph. They still wouldn't have to pay a dime. As in, who cares if they would have to offer the source to something where the source is already available.

      The GPL is not the godsend that many people believe it to be. In fact, if looking at current (and past) business practice is any indication, the GPL would have actually hindered OpenSSH's adoption, not promoted it. Businesses really hate that viral open source thing in the GPL regardless of whether there code actually touches the GPL'd code. Just not worth the risk for many (most?).

      • Re: (Score:3, Interesting)

        by rtfa-troll (1340807)

        Businesses really hate that viral open source thing in the GPL

        You seem to think that we're on some ideological crusade to take over everything. In the real world, we just don't care at all about anything which is not "core business". The GPL is an excellent thing since we can give back source code without much need to think. The business justification is one check box (because we have to) rather than weeks of meetings about whether this feature is strategic. When you somehow end up giving away a feature to a GPL app, you know that even if the competition gains the

    • Re:License (Score:5, Insightful)

      by onefriedrice (1171917) on Friday October 02, 2009 @02:16AM (#29614261)

      Not wanting to troll but, you know, if openssh was GPL licensed said commercial vendors would have to release the source for openssh with their products, including any modifications they made. The project could also offer LGPL or BSD licensed versions in exchange for cold, hard, cash.

      Instead they do the noble thing and release their hard work without strings attached. They understand the alternatives but actively choose to stick with a license that doesn't childishly punish those who cannot or won't return the favor. They do what they do not to "stick it" to corporations but rather because they love to code and love when their code is used to improve peoples' lives. They even love it when somebody is able to take what they've done and build off of it or incorporate it into a product. It's a matter of love, and love must be given without strings and viral conditions. It's true charity, and charity is for the giver as much as the receiver. It's the BSD philosophy, and it's not often understand by the GNU herd. But that's okay, because the software we write is for them, too. And we love it even if they don't understand why.

      Thanks OpenBSD. You're awesome. I hope a lot of people today make good use of this link [openssh.com].

      • Re: (Score:3, Interesting)

        by rohan972 (880586)
        The constant pissing match between GPL and BSD advocates is a bit silly IMO. It seems to me (not being a programmer but being a user of BSD and GPL licensed software) that each licence is appropriate for difference circumstances, according to the desires of the author.

        It's like arguing that knives are superior to forks, so I only eat with knives! Licenses are a tool, each suitable for it's purpose.

        I don't agree that the GPL "childishly punishes" anyone, nor that it is viral. It is copyright that provi
      • Re:License (Score:4, Insightful)

        by Kjella (173770) on Friday October 02, 2009 @04:21AM (#29614695) Homepage

        Meh, check out Theo's wikiquote [wikiquote.org] page:
        "So the HP guy comes up to me (at the Melbourne conference) and he says, 'If you say nasty things like that to vendors you're not going to get anything'. I said 'no, in eight years of saying nothing, we've got nothing, and I'm going to start saying nasty things, in the hope that some of these vendors will start giving me money so I'll shut up'."

        Doesn't sound much like "love" or "charity" to me. Sounds to me like a man that's tried of giving and giving and giving and never getting anything back, yet refuses to acknowledge that as long as the license doesn't require anyone to give anything back, corporations don't. Their obligations are to the stockholders, not to fair dealings. Squeeze your costs as much as possible, get as much money as possible out of your customers, turn a big profit. That's what drives most companies all the time and all companies most of the time. Theo seems to be going by much the same drive as Linus, he wants to do this "right", he wants to make the best possible product. But unlike Linus, he hasn't gotten everyone else on board.

        It's possible what is in OpenBSD is better, per se. But compared to Linux it's like an obscure niche site compared to wikipedia, it's where everyone contributes and it's huge, hard to manage but ends up being so much more useful. You got people working on Linux to make it run better on everything from cell phones to supercomputers. You got people working on getting all sorts of wierd hardware work. You got people working on desktop responsiveness and heavy server workloads. You got all sorts of research work, build farms and regression tests being run all over the place. OpenSSH may be a polished gem, but it's only the front door lock. But for everything else if you're relying on the masses to develop your OS, I'm going where the masses are. That is in no small part the license, though I know there's also other reasons...

  • Fast, Weak sshfs (Score:3, Interesting)

    by Doc Ruby (173196) on Friday October 02, 2009 @12:43AM (#29613951) Homepage Journal

    I find sshfs to be a much easier to use ad-hoc network fileystem mounter than the other popular alternatives. And it's secure by default.

    But it's too secure. Or rather, there are scenarios in which the network transfer doesn't need the ssh security, but encrypting it takes too long (or too much CPU from other tasks, especially on dinky embedded network devices). Is there a way to force sshfs to use a much less compute intensive encryption, or maybe even a null crypto module? Without hacking the source directly, that is - like an execution option, a compile option, a config rule, etc.

    • by Rennt (582550)

      A null-crypto secure-shell file-system?

      Two thoughts spring to mind - "Why?" and "NFS"

      • by shish (588640)

        "Why?" and "NFS"

        Each of those are the answer to the other -- NFS is the only real alternative, and it is awful; SSHFS is simpler to set up, simpler to use, more reliable, more flexible, more secure (even when I'm on a LAN and don't want encryption, I still want authentication), etc...

    • Wait, you want ssh to not be secure? wtf! Just use cifs if you don't like the encryption.

      • by shish (588640)

        Wait, you want ssh to not be secure? wtf! Just use cifs if you don't like the encryption.

        What if you don't like the encryption, but you do like the ease of setup, ease of use, flexibility, reliability, etc?

    • by Kjella (173770)

      I don't think the OpenSSH guys want to add it, and I agree with them. It's a tool used by so many that understand so little, but at least they've sorta understood that SSH = secure. They'd still fall for any certificate trickery because they don't really understand, but I digress. The point is that once sshfs means maybe secure, maybe not secure you can bet idiots will do stuff like disable crypto and go "Hey look, it's still ssh, it's still secure, and it's 100x faster" and completely ignore all the blinke

  • I love that they implemented multiplexing channels ... -R and -L are just awesome.

    • Re: (Score:3, Interesting)

      by TheRaven64 (641858)
      There are a few features in ssh related to that that a lot of people seem to be completely unaware of. The -D option runs a SOCKS4/5 proxy on a given port, which can dynamically forward things for you. As long as your client app supports SOCKS proxies, it will work transparently through this, forwarding ports as required. The -w option lets you set up the tun(4) device for forwarding. You can use this to forward at the IP or Ethernet layer. It gives you a virtual network device that forwards every fram
  • is it better than telnet?????

  • by Cato (8296) on Friday October 02, 2009 @03:13AM (#29614475)

    One of the best things about SSH is rsync - you only need an SSH enabled login on a machine, with a copy of rsync, to be able to efficiently copy data with block-level incremental efficiency. Even better, there are excellent backup tools such as rsnapshot that build on rsync to store multiple versions of a file in the backup file tree, using hard links to avoid storing the same version twice - so every backup is a full backup in terms of easy recovery, but an incremental backup in terms of network and storage efficiency.

    See http://slashdot.org/comments.pl?sid=1371703&cid=29451267 [slashdot.org] for more about rsnapshot and friends.

  • The fact that the editors thought that Slashdot needed an explanation of what OpenSSH is makes me feel dirty. It is like explaining what H2O is. If you don't know what OpenSSH is you should not be reading Slashdot, you bastards!

  • Did they fix the hole that allowed imageshack and such to get hacked a while back? Did they ever even find out what that hole was?

    (The hackers claim 5.2 is safe, but for all we know, that could be a trick to make us upgrade to an even buggier version... the hack was in the name of avoiding full disclosure, so we'll probably never know exactly what they did, and thus not be sure it's fixed, and thus the incredibly anti-full-disclosure people demonstrate exactly why full disclosure is a good thing :-/ )

  • by chrysalis (50680) on Friday October 02, 2009 @04:04AM (#29614625) Homepage

    Unfortunately, on OSX, while the option (-w) is documented, OpenSSH still doesn't support tunneling, even after installing tuntap.

  • by fialar (1545) on Friday October 02, 2009 @04:35AM (#29614733)

    http://lwn.net/Articles/354891/ [lwn.net]

    Otherwise, OpenSSH is fantastically secure. :)

  • Does it run... (Score:3, Interesting)

    by Aladrin (926209) on Friday October 02, 2009 @06:54AM (#29615113)

    Yes but, does it run on Windows 7?

    I tried installing sshwindows on Win7 the other day and the service wouldn't start. As far as I can tell, openssh has never officially supported Windows and never will.

    Sure, it's useful for 'nix to 'nix connections, but I need my Windows PC in on the action, too.

    • Sure. (Score:3, Interesting)

      by Pegasus (13291)

      Install cygwin or Microsoft'w own SFU (services for unix). They give you sshd under windows, init scripts, NFS mounting etc. SFU is actually based on openbsd userspace.

Thus spake the master programmer: "After three days without programming, life becomes meaningless." -- Geoffrey James, "The Tao of Programming"

Working...