#27255: autossh defaults to using /usr/bin/ssh even with macports ssh installed --------------------------------+------------------------------------------- Reporter: chiggsy@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: autossh --------------------------------+------------------------------------------- Comment(by chiggsy@…):
Daniel and Rainer raised some objections to this in [http://lists.macosforge.org/pipermail/macports- users/2010-November/022585.html the mailing list discussion] that prompted the filing of this ticket.
I can check that discussion but the fact remains that autossh, as currently offered by macports, defaults to an ssh program outside of the macports tree. /usr/bin/ssh looks to /etc for it's configuration, not /opt/local/etc. That's really an issue: You install openssh, you configure it, in /opt/local/etc , since after all, macports is advertised to only look in /opt/local, you run it autossh, and instead of using the updated, patched version of openssh you most likely installed openssh to get, you are using whatever version Apple bothered to release. I simply need to bring up the 2 year delay in patching BIND, or the recent drive by PDF bug that made jailbreaking so easy, to raise valid concerns about commercial vendors patching speed. IMO ssh is a key tool, and if nothing else, it should be advertised that macports will , oddly , and silently, default to an unexpected program, while using the most standard way to achieve a secure shell. All the man pages for the programs involved are from /opt/local . What clue would I have that /usr/bin/ssh would be run? My mistake, strings /opt/local/bin/autossh shows /usr/bin/ssh. Any user, reading the documentation, would assume that /opt/local was the default tree. I maintain that -- Ticket URL: <https://trac.macports.org/ticket/27255#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS