|
|
Log in / Subscribe / Register

OpenSSH 5.7 released

OpenSSH 5.7 released

Posted Jan 25, 2011 5:31 UTC (Tue) by madscientist (subscriber, #16861)
In reply to: OpenSSH 5.7 released by nix
Parent article: OpenSSH 5.7 released

According to what I read, the "symlink" command used to work in previous versions and still does here. It does involve changes if you used "ln" instead of "symlink", but (at least if I understood what was meant by "preexisting [...] command") you can have a single syntax that works across multiple versions.


to post comments

OpenSSH 5.7 released

Posted Jan 25, 2011 21:07 UTC (Tue) by Tobu (subscriber, #24111) [Link] (4 responses)

The change is bad API design for three reasons:

  • It didn't introduce a reliable hardlink feature. This is because there is no way to say "make a hardlink" and know it succeeded. If you use ln and the server is old, it will make a symlink; if it is new, it will make a hardlink.
  • It broke compatibility with clients that used ln to symlink. Those clients get behaviour that couldn't be anticipated at the time they were written, and need to be rewritten to use symlink instead.

What is actually afforded that couldn't be done before is the option to hardlink from the sftp protocol when the server supports it, detecting the feature using the method nix suggested (try "ln -s" once, failure means ln symlinks), which may break if the OpenSSH developers keep changing the behaviour of existing commands. If the feature isn't supported it is still possible to say "upgrade your sshd" or to reimplement ln using ssh commands instead of sftp commands. If you start with the second option you'll be mixing two protocols, and ditching the sftp protocol can become more attractive.

The "extra" API is hard to use and easy to misuse, and it doesn't provide a lot of value when compared to rolling your own. It also broke existing API for no good reason.

OpenSSH 5.7 released

Posted Jan 25, 2011 21:09 UTC (Tue) by Tobu (subscriber, #24111) [Link]

(two reasons. I can't count, or I edit too much)

OpenSSH 5.7 released

Posted Jan 25, 2011 23:33 UTC (Tue) by nix (subscriber, #2304) [Link]

Quite so.

It would be tolerable if this was the only time they'd done it... but it's the third or fourth, and my initially-simple interaction scripts have had to compensate for all of them :(

OpenSSH 5.7 released

Posted Jan 29, 2011 23:18 UTC (Sat) by jamesh (guest, #1159) [Link] (1 responses)

From the description of the change, there are two parts: an addition to the SFTP protocol, and support for said extension in the bundled client implementation.

If you use an old client against a new server, you should notice no difference. If you use a new client against an old server, presumably it will complain when you send it an unknown command if you try to create a hard link.

OpenSSH 5.7 released

Posted Jan 31, 2011 22:09 UTC (Mon) by Tobu (subscriber, #24111) [Link]

I found the relevant internet draft (2006). Apparently the protocol has supported hardlinks for a while, and the broken design is strictly client side. That can be version checked (with the package manager, because there is no --version). I'm not about to check the openssh source diff though.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds