Slashdot Mirror


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

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."

67 of 249 comments (clear)

  1. I know I'm not alone in this... by 93+Escort+Wagon · · Score: 5, Insightful

    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!

    --
    #DeleteChrome
    1. Re:I know I'm not alone in this... by e9th · · Score: 4, Informative

      Please consider buying one or more of their so-ugly-they're-cute T-shirts.

    2. Re:I know I'm not alone in this... by grub · · Score: 3, Insightful


      Slashdot is a news site. We don't need to be notified every time something exists for 10 years. Unless this "encrypting traffic" thing is new in OpenSSH v5.3

      It's not new to OpenSSH but OpenBSD's default disabling of telnet (when everyone used it) and pushing OpenSSH helped make secure connections the standard.

      --
      Trolling is a art,
    3. Re:I know I'm not alone in this... by nametaken · · Score: 4, Funny

      Or donate some decent t-shirt designs. :/

    4. Re:I know I'm not alone in this... by TheRaven64 · · Score: 4, Informative

      OpenSSH is developed by OpenBSD. They accept PayPal donations via the link on this page.

      --
      I am TheRaven on Soylent News
  2. Happy birth-day OpenSSH by La+Gris · · Score: 2, Funny

    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

    --
    Léa Gris
    1. Re:Happy birth-day OpenSSH by CSMatt · · Score: 2, Funny

      3) I'm a snake
      5) I live in a data-center

      Huh?

    2. Re:Happy birth-day OpenSSH by dragonturtle69 · · Score: 2, Funny

      I think something was lost in the translation in that post, French to English.

      --
      "What luck for the rulers that men do not think." - Adolph Hitler
    3. Re:Happy birth-day OpenSSH by holloway · · Score: 4, Funny

      3) I'm a snake

      Huh?

      Step 4 ????
      Step 5 Badger badger badger badger badger

  3. And best of all... by Timothy+Brownawell · · Score: 2, Insightful

    ...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).

  4. Thanks OpenBSD by Spit · · Score: 4, Insightful

    For the rest as well.

    --
    POKE 36879,8
    1. Re:Thanks OpenBSD by atheistmonk · · Score: 3, Insightful

      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.

    2. Re:Thanks OpenBSD by JackieBrown · · Score: 4, Interesting

      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

    3. Re:Thanks OpenBSD by Dadoo · · Score: 3, Informative

      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.

      --
      Sit, Ubuntu, sit. Good dog.
    4. Re:Thanks OpenBSD by Anonymous Coward · · Score: 4, Insightful

      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.

    5. Re:Thanks OpenBSD by Chris+Pimlott · · Score: 2, Informative

      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.

    6. Re:Thanks OpenBSD by impaledsunset · · Score: 2, 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.

    7. Re:Thanks OpenBSD by Hatta · · Score: 3, Interesting

      OpenSSH provides a lot more than just security. Sometimes I'd just like it to forward X over my LAN. In that case, encryption is completely unnecessary. Yeah, I could do it the old fashioned way, but it's been so long I've forgotten how.

      --
      Give me Classic Slashdot or give me death!
    8. Re:Thanks OpenBSD by gad_zuki! · · Score: 2, Informative

      >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.

  5. How was life possible without it? by stox · · Score: 5, Insightful

    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.

    --
    "To those who are overly cautious, everything is impossible. "
    1. Re:How was life possible without it? by the_humeister · · Score: 3, Funny

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

    2. Re:How was life possible without it? by Anonymous Coward · · Score: 3, Insightful

      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.

    3. Re:How was life possible without it? by InsaneMosquito · · Score: 4, Funny

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

      A lot more drafty?

    4. Re:How was life possible without it? by grub · · Score: 4, Funny


      What would life be like without zippers?

      I'd have far fewer painful memories of getting wang-skin caught in them.
      R

      --
      Trolling is a art,
    5. Re:How was life possible without it? by evil_aar0n · · Score: 2, Insightful

      Just a suggestion, but maybe you should wear underwear... Of course, there are situations where you have to zip-and-dash, like when your girlfriend's husband walks in, unannounced - the nerve... - but, generally, I've found that the judicious use of Underoos helps prevent biting zip-ups.

      --
      Truth, Justice. Or the American Way.
    6. Re:How was life possible without it? by evilviper · · Score: 5, Informative

      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.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    7. Re:How was life possible without it? by wastedlife · · Score: 4, Funny

      I have a pair of 404s, but I can never find them.

      --
      Said, "It's just like dice but it's got more sides And it tells me who lives and who dies"
    8. Re:How was life possible without it? by RzUpAnmsCwrds · · Score: 3, Funny

      I have a pair of 413s, but they are too big to fit me.

    9. Re:How was life possible without it? by Anonymous Coward · · Score: 5, Interesting

      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.

    10. Re:How was life possible without it? by AliasMarlowe · · Score: 2, Funny

      I have a pair of 404s, but I can never find them.

      You can get as many 419s as you can handle from my colleague, until recently the Esteemed Excellency of Nigeria's Department of Overseas Resource Depletion, and now with a large number of undocumented 419s at his disposal. Please reply with banking details, home address and SIN, and all other useful information such as drivers license and credit card numbers.

      --
      Those who can make you believe absurdities can make you commit atrocities. - Voltaire
  6. 10 years of fear reading sec lists by VonGuard · · Score: 5, Insightful

    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.

    --
    Don't Crease the Weasel!
  7. i dont need ssh by digitalsushi · · Score: 4, Funny

    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.

    --
    slashdot: where everyone yells sarcastic metaphors to themselves to understand the issue
    1. Re:i dont need ssh by dazjorz · · Score: 3, Funny

      Interesting. Would you mind telling me what host and port this is, so I can.. um... diagnose the uh.. problem?

    2. Re:i dont need ssh by MichaelSmith · · Score: 5, Funny

      All that gives me is a web page with tentacle porn....

    3. Re:i dont need ssh by David_W · · Score: 5, Funny

      since lately i can't even seem to remember what my password is

      It's hunter2.

    4. Re:i dont need ssh by glittalogik · · Score: 3, Funny

      Live action or animated? Normally I wouldn't pry but my genitals wanted me to ask.

    5. Re:i dont need ssh by Anonymous Coward · · Score: 5, Informative

      For the young folk who are scratching their heads...

      http://www.bash.org/?244321

    6. Re:i dont need ssh by noidentity · · Score: 3, Funny

      "since lately i can't even seem to remember what my password is"

      It's hunter2.

      That's odd; it just appears as ******* to me. Is that because it only shows up for the person whose password it is? Cool.

  8. Re:but does it... by stinkytoe · · Score: 2, Informative

    Ditto for android.

  9. Is OpenSSH still speed limited? by TheSlashaway · · Score: 2, Insightful

    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/

    1. Re:Is OpenSSH still speed limited? by 0123456 · · Score: 2, Interesting

      Yeah, scp gets about 55MB/sec between Linux systems at work with gigabit LAN.

    2. Re:Is OpenSSH still speed limited? by WuphonsReach · · Score: 4, Informative

      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.

      --
      Wolde you bothe eate your cake, and have your cake?
  10. To the best by Powys · · Score: 4, Insightful

    My hats off to probably the best open source package ever made

    1. Re:To the best by turing_m · · Score: 4, Funny

      Have you checked out my package?

      --
      If I have seen further it is by stealing the Intellectual Property of giants.
    2. Re:To the best by alx5000 · · Score: 2, Funny

      Is open sores close enough?

      --
      My 0.02 cents
    3. Re:To the best by hiekka · · Score: 2, Funny

      Have you checked out my package?

      Wow, is that bzipped? How large is it uncompressed?

    4. Re:To the best by turing_m · · Score: 2, Funny

      Wow, is that bzipped? How large is it uncompressed?

      Of course it's bzipped - but I'm not sure what the compression ratio is for Python. I'd appreciate it if you wouldn't fork it. And be careful when examining the Python, it has been known to generate streams of Perl. You'd rather not get it on you - it is, after all, a glue language.

      --
      If I have seen further it is by stealing the Intellectual Property of giants.
  11. I remember switching to openSSH. by Vellmont · · Score: 4, Interesting

    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.

    --
    AccountKiller
  12. Re:but does it... by MichaelSmith · · Score: 2, Informative

    run on iPhone?

    It sure does. TouchTerm, for example, uses OpenSSH.
    http://jbrink.net/touchterm/

    Not the server though.

  13. Re:License by Yosho · · Score: 2, Insightful

    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?

    --
    Karma: Terrifying (mostly affected by atrocities you've committed)
  14. Fast, Weak sshfs by Doc+Ruby · · Score: 2, Interesting

    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.

    --

    --
    make install -not war

    1. Re:Fast, Weak sshfs by rohan972 · · Score: 2, Funny

      That said, i never knew there was such a thing as "too secure"

      You've never lost the key to the blast proof underground safe you keep your asthma medication in obviously.

    2. Re:Fast, Weak sshfs by TheRaven64 · · Score: 2, Informative

      NFS4 is starting to be quite well supported (Linux, Solaris, FreeBSD and - I think - OS X now implement it) and supports encryption. It uses a very different model to things like CIFS and SSHFS though. NFS is designed for sharing filesystems to computers, while CIFS and SSHFS are designed for sharing filesystems to users. This is a critical distinction. A user can mount a remote share using one of these protocols, with their own credentials, and use it. NFS (or AFS and derivatives) requires the administrator to set up the mounts and make sure authentication between the two machines (Kerberos or similar) works, but then it's completely transparent to users. The others are much easier for ad-hoc shares.

      --
      I am TheRaven on Soylent News
  15. Re:License by Secret+Rabbit · · Score: 3, Insightful

    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?).

  16. Re:License by onefriedrice · · Score: 4, Insightful

    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.

    --
    This author takes full ownership and responsibility for the unpopular opinions outlined above.
  17. Re:License by rtfa-troll · · Score: 2, Interesting

    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 same, they still have to make any fixes they make available to other people.

    Speaking for most "businesses" everywhere.

    --
    =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
  18. what is this 'ssh'? by dogganos · · Score: 2, Funny

    is it better than telnet?????

  19. rsync over SSH for backups by Cato · · Score: 4, Informative

    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 for more about rsnapshot and friends.

  20. Re:License by rohan972 · · Score: 3, Interesting

    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 provides the "virality" (virusness?), not the GPL, and even BSD has the requirement of attribution making it just as viral (through copyright) though with less onerous conditions.

  21. Still no tunneling on OSX by chrysalis · · Score: 2, Interesting

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

    --
    {{.sig}}
    1. Re:Still no tunneling on OSX by TheRaven64 · · Score: 2, Informative

      The -w option creates a virtual network adaptor and forwards IP packets or Ethernet frames over it. If you use it in Layer 3 (IP) mode then it will forward TCP, UDP, SCTP, and any other IP protocol. If you use it in Layer 2 mode then it will also work with non-IP protocols, such as AppleTalk. -L and -R, in contrast, only work with TCP. Both of these support routing, so your client can connect to any arbitrary server on any port and have packets passed along the encrypted connection as the first hop. This allows you to set up a VPN quite trivially. For example, you can use ssh with -w between two machines in different LANs, configure forwarding between their tun device and their physical Ethernet device, and have things like AppleTalk printers on one LAN accessible to the other. p. A half-way step is -D, which sets up a SOCKS proxy on the client machine, forwarding connections to the server. This requires the client to support SOCKS proxies, but a lot of things do these days.

      --
      I am TheRaven on Soylent News
  22. Re:License by Kjella · · Score: 3, Insightful

    Meh, check out Theo's wikiquote 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...

    --
    Live today, because you never know what tomorrow brings
  23. Beware of Linux-induced vulnerabilities by fialar · · Score: 2, Interesting

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

    Otherwise, OpenSSH is fantastically secure. :)

  24. Re:but does it... by icebike · · Score: 2

    Seriously, how did parent get modded flamebate?

    You Apple fanboys have to back off a little bit. Apple is a big company, they don't need you to rush to their defense every time some one posts a disparaging word.

    And the truth, as the parent posted, can not be a flame.

    --
    Sig Battery depleted. Reverting to safe mode.
  25. Does it run... by Aladrin · · Score: 2, Interesting

    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.

    --
    "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
  26. Re:tunneling by TheRaven64 · · Score: 2, Interesting

    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 frame or packet (depending on whether it's L2 or L3) to the matching interface on the other machine. You can use this to set up VPNs quite easily.

    --
    I am TheRaven on Soylent News
  27. Sure. by Pegasus · · Score: 2, Interesting

    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.