Ssh stopped working after upgrading to 10.4.7

Question

Since I upraded to 10.4.7, ssh won't work anymore on my MBP, giving a Segmentation Fault error message. I would appreciate a lot any ideas for what could be going wrong.

Answer 1

well i would guess that some file got corrupted or you have a messed up environment that is causing a wrong version of some library to load
so first check the md5 of ssh, and check what its linked against, see if anything i posted below differs from what you get
md5sum /usr/bin/ssh
6580fb56274da1a3639dadc55e032a24 /usr/bin/ssh
ldd /usr/bin/ssh
/lib/libsafe.so.2 (0xb7fc4000)
linux-gate.so.1 => (0xffffe000)
libresolv.so.2 => /lib/tls/libresolv.so.2 (0xb7f82000)
libcrypto.so.0 => /usr/lib/libcrypto.so.0 (0xb7e4a000)
libutil.so.1 => /lib/tls/libutil.so.1 (0xb7e46000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7e34000)
libnsl.so.1 => /lib/tls/libnsl.so.1 (0xb7e1e000)
libcrypt.so.1 => /lib/tls/libcrypt.so.1 (0xb7def000)
libc.so.6 => /lib/tls/libc.so.6 (0xb7cc0000)
libdl.so.2 => /lib/tls/libdl.so.2 (0xb7cbc000)
/lib/ld-linux.so.2 (0xb7fca000)
if that doesn't find it, then type `gdb /usr/bin/ssh`, then type "run" to start ssh, that will run ssh as normal but when it segfaults you will be able to type "bt" to generate a backtrace that should at least tell you what file was getting executed when it crashed, that file will probably be causing it because of their a miss-matched version or it could be corrupted, if unsure post the backtrace