Josh Kuperman wrote:
> The System Update notified me of an update to OS X's OpenSSH to
> 3.4pl1, along with some other programs. Is there any problem, for me
> as an OS X user with an iMac,  with my simply using the Mac
> distributed SSH as opposed to the Fink distributed version.

IMHO after the July2002 security update, there is no reason to use 
Fink's openssh right now.

> If I simply remove the Fink version will I still preserve whatever
> keys and settings I had, when I try to use the Apple distributed
> version.

You preserve everything that is in your own ~/.ssh folder, basically 
your keys. OTOH, the machine's keys and the config files are at 
different places: Fink has them in /sw/etc/ssh/, Apple in /etc/. I think 
it is safe to copy the contents of /sw/etc/ssh/ over to /etc/. The 
formats are the same, and AFAICT the security update does not touch 
these files (a fact which appears strange to me, seeing that for example 
  /etc/sshd_config has not changed on this machine here since the 10.0.4 
system upgrade.

One word of warning: If you have Fink's openssh-3.4p1-1 installed and 
remove it, check if your /var/ directory (as a symlink to /private/var/) 
is still there. If not, recreate the symlink, otherwise all kinds of bad 
things happen (network is dead, system preferences are not remembered, 
and rebooting gets somewhat tricky...) The new version 3.4p1-2 solves 
this problem, but I don't know if the problem with the not existing 
privilege separation user sshd is solved or if one has to jump through 
some hoops to solve it. Apple's new version doesn't seem to need it 
(perhaps because, contrary to what the new man sshd_config says, 
UsePrivilegeSeparation does *not* default to yes).

-- 
Martin







-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
No, I will not fix your computer.
http://thinkgeek.com/sf
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to