Hello all -- I have a question regarding security. I noticed that there is a well-maintained port, openssh, which as of a few weeks ago (I haven't re-synced my ports lately) uses OpenSSH version 5.0p1 ...
What is interesting is that as of Mac OS X Server 10.5.2 (and also non-Server I noticed on an iMac Mac OS X 10.5.4), Apple's uses version 4.7p1 (although interestingly Mac OS X Server 10.5.1 uses OpenSSH 4.5p1 so Apple had a rapid change of heart from 10.5.1 Server to 10.5.2 Server which seems uncharacteristic of Apple). Apple's instance of OpenSSH is installed in /usr/bin and of course this is not logically the same location recommended for a MacPorts prefix. All of this begs the question, how do most MacPorts community members use the MacPorts installed version of OpenSSH on a Mac when in fact Apple's providing a different version? Doesn't this create conflicts? Ro avoid conflicts, how does one override Apple's plumbing of OpenSSH which they've integrated with a launchd plist? For example, there is Apple's installation of this resource: /System/Library/LaunchDaemons/ssh.plist > Taking a look at the guts of that plist, it appears that the sshd (daemon) is invoked on an as needed basis (thus the benefits of launchd). Do most MacPorts users (who elect to port install openssh) end up hacking Apple's ssh.plist to re-plumb with the version of ssh that ends up in the MacPorts prefix? Thank you for any insights, -T.M.
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
