Slashdot Mirror

← Back to Stories (view on slashdot.org)

OpenSSH 3.5 Released

Posted by timothy on from the vavavoom dept.

Dan writes "Markus Friedl announces that OpenSSH 3.5 has just been released with notable updates since 3.4. It will be available from the mirrors listed at http://www.openssh.com/ shortly. Enhancements include bug fixes, improved support for Privilege Separation (Portability, Kerberos, PermitRootLogin handling), RSA blinding in order to avoid timing attacks against the RSA host key and much more. Congratulations are in order for the OpenSSH team's hard work and efforts."

8 of 140 comments (clear)

  1. Check those MD5s! by egg+troll · · Score: 5, Informative

    Remember to check the MD5s of those downloads this time around!

    --

    C - A language that combines the speed of assembly with the ease of use of assembly.
  2. Re:Stupid question.. by Kwikymart · · Score: 5, Informative

    The same people that make OpenBSD make OpenSSH?

    Whenever some story about, say KDE, pops up everyone is like "this is the best thing for Linux since sliced bread". Reality check: not all people run KDE run it on Linux. I think the BSD people should be entitled to the same "This is what we do for everyone!" type of recognition as everyone else.

    --

    Buying a Dell computer is equivalent to dropping the soap in a prison shower.
  3. Re:MD5 is just a hash... by wirelessbuzzers · · Score: 5, Informative

    They do have a GPG detached sig. The portable version is signed by Damien Miller (and verified, and it matches the MD5), for example. But, on the other hand, Damien miller's key has no sigs on it, so there's no reason for us to believe that it really belongs to him...

    So, in the end, you're just going to have to trust that *somebody* isn't out to get you, unless you want to run through the source code line-by-line... ...Or, you can download it now, wait a few days (faster than examining the source), and see if they post "OpenSSL trojaned!!" to the front page of Slashdot, then install it. Take your pick.

    --
    I hereby place the above post in the public domain.
  4. Re:Debian by crimsun · · Score: 4, Informative

    There's a fair amount of testing that takes place before the packages are updated. I wouldn't count on 3.5pX going into Sid for a while yet. The more critical fixes might be backported against 1:3.4p1-4, etc.

  5. Re:RSA by Permission+Denied · · Score: 5, Informative
    print pack"C*",split/\D+/,`echo "16iII*o\U@{$/=$z;[(pop,pop,unpack"H*",
    )]}\EsMsK sN0[lN*1lK[d2%Sa2/d0

    NO CARRIER

    You again. Excellent troll, but you need to choose a different motif for your nicks.

    For the uninitiated: that is not perl. It is line noise with some perl operators, bundled into a cleverly-masked troll. This guy is an old sport at this, previously using the name "PhysicsGenius". Check his (short) user history, and this guy's posting history. I simply cannot believe that moderators would be so idiotic as to mod this stuff up, so my conjecture is that he has two accounts: one to troll, and another serious account with mod points. It may be interesting to correlate average time between mod points to his posting history.

    Relevant anecdote: the original OpenSSH sources had an "RSA in six lines of perl" in a comment of one of the source files. Theo removed that in some version. A little too much angst there, if you ask me - this stuff is supposed to be fun.

  6. Re:Where is the public key to check the sig? by mmca · · Score: 4, Informative

    I agree. Look for djm@mindrot.org on your favorite keyserver. (I like the one below)

    http://pgp.mit.edu:11371/pks/lookup?op=get&searc h= 0x86FF9C48

    M

  7. Re:My one bugbear by Phibz · · Score: 4, Informative
    I've used the scp-wrapper perl script and it works excellently. I add a dsa key for the client and in the key in authorized_keys i add command="/usr/sbin/scp-wrapper" ......

    Basically what the script does is clean the environment. The requested command is stored in SSH_ORIGINAL_COMMAND environmental variable. Its checked to make sure it is in fact the command you intend. The options are then checked. Finally the script exec()'s the hardcoded path to the command with arguments supplied.

    Although it comes written for scp i've used it for securing an account so they can't log in, and they can only execute one or two commands of my choosing.

    from what i understand sftp just exec's /usr/libexec/sftp-server. i don't see why you couldn't alter the script to only allow that command.

    also you'll want to make sure the client's ~/.bash_profile, ~/.profile, etc.--all its login scripts--are empty and owned by root so that they don't upload their own "special" login script and undo all your work.

    scp-wrapper can be found here

    Phibz

  8. Re:Slow Down by dmiller · · Score: 5, Informative

    Firstly, do you patch all local privilege escalation vulnerabilities as quickly as you patch remote vulnerabilities? I know I don't.

    Please RTFM: An attacker breaking privsep will find themselves in an empty chroot jail with a unique, non-priviliged UID & GID. Leveraging such an attack to even read local files would be very difficult.

    Your points about a broken privsep being used to stage network-based attacks are valid.