Hi all

Running 10.2.6, Build 6L60. Software Update did its weekly auto-run
tonight, and found Security Update 2003-08-14. I installed it. Upon
reboot, I now have the following problems:

1) I wasn't able to get a shell in Terminal (I've since fixed this). It
would segfault and dump to Library/Logs/CrashReporter/login.crash.log.

2) sshd no longer accepts connections, though it continues running. Upon
a connection attempt, it dumps to sshd.crash.log.

3) I cannot su from a shell prompt. It segfaults and dumps to
su.crash.log.

I stumbled across a fix for the first problem by opening Terminal,
looking in the Prefs dialog, and changing the setting from "Execute the
default login shell using /usr/bin/login" to "Execute this command:
/bin/bash" ... If I try to run /usr/bin/login, it segfaults.

Problems 2 and 3 still exist. The affected binaries look thusly:

-r-sr-xr-x 1 root wheel 21948 Aug 19 02:10 /usr/bin/login
-r-sr-xr-x 1 root wheel 20100 Aug 19 02:10 /usr/bin/su
-rwxr-xr-x 1 root wheel 311808 Aug 19 02:10 /usr/sbin/sshd
MD5 (/usr/bin/login) = a8e9046a486476f500ef5cf2746a8151
MD5 (/usr/bin/su) = 72136e3f97367e2ab6c79972f6a14960
MD5 (/usr/sbin/sshd) = 4feb18ada792645e90c7f43e3f9b6eb0

I'm alarmed that sshd is writeable, though the modification date does
match the time at which I performed the System Update. Other binaries
which were updated at the same time work fine (e.g. curl, top).

I tried disabling and re-enabling the root account to no avail. I also
ran the Disk Utility and did a permissions fix, no luck there either.
Finally I tried manually downloading Security Update 2003-08-14 from
Apple with the hopes of reinstalling, but after getting past the
license, it tells me that my drive is not eligible for the update. So
much for that idea.

Has anyone experienced similar problems after installing this most
recent patch, and/or does anyone have any suggestions for attempting to
fix the problems?

Thanks!