After Security Update today: "Bus error" when starting "ssh" client

I'm still investigating hoping as I'm sure we all are that we can find a workaround before Apple comes around with a fix. One interesting thing I found so far though is that "sudo ssh" seems to work for me just fine while ssh in my user account's context yields a bus error.

The new one reports version (ssh -V) as: OpenSSH_4.7p1, OpenSSL 0.9.7l 28 Sep 2006

The one it replaced gives: OpenSSH_4.5p1, OpenSSL 0.9.7l 28 Sep 2006

4.7 and 4.7p1 are the current versions from OpenSSH. Past versions are available in the old directory on the ftp site (mirrors are listed by country, go to openssh.org to start).

Same here.

Process: ssh [526]
Path: /usr/bin/ssh
Identifier: ssh
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: bash [504]

Date/Time: 2008-03-19 02:24:55.166 +0100
OS Version: Mac OS X 10.5.2 (9C31)
Report Version: 6

Exception Type: EXC BADACCESS (SIGBUS)
Exception Codes: KERN PROTECTIONFAILURE at 0x0000000000001014
Crashed Thread: 0

Thread 0 Crashed:
0 ??? 0x0004c4e7 0 + 312551
1 ??? 0x0004c56e 0 + 312686
2 ??? 0x0004c7f7 0 + 313335
3 ??? 0x0004b070 0 + 307312

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00001000 ebx: 0x0004c7d5 ecx: 0x0004e338 edx: 0x0004e340
edi: 0x0000101c esi: 0x00000000 ebp: 0xbffffa38 esp: 0xbffffa10
ss: 0x0000001f efl: 0x00010282 eip: 0x0004c4e7 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00001014

Binary Images:
0x2340d000 - 0x2344afef +ssh ??? (???) <38f6d3ec24f0b372e64c12b15bb319d4> /usr/bin/ssh
0x8fe00000 - 0x8fe2da53 dyld 96.2 (???) <7af47d3b00b2268947563c7fa8c59a07> /usr/lib/dyld
0x9019f000 - 0x901a6fe9 libgcc_s.1.dylib ??? (???) <a9ab135a5f81f6e345527df87f51bfc9> /usr/lib/libgcc_s.1.dylib
0x901a7000 - 0x901aeffe libbsm.dylib ??? (???) <d25c63378a5029648ffd4b4669be31bf> /usr/lib/libbsm.dylib
0x90fe6000 - 0x91004fff libresolv.9.dylib ??? (???) <0629b6dcd71f4aac6a891cbe26253e85> /usr/lib/libresolv.9.dylib
0x91c8d000 - 0x91d6cfff libobjc.A.dylib ??? (???) <a53206274b6c2d42691f677863f379ae> /usr/lib/libobjc.A.dylib
0x91d87000 - 0x91e39ffb libcrypto.0.9.7.dylib ??? (???) <330b0e48e67faffc8c22dfc069ca7a47> /usr/lib/libcrypto.0.9.7.dylib
0x92111000 - 0x92249ff7 libicucore.A.dylib ??? (???) <afcea652ff2ec36885b2c81c57d06d4c> /usr/lib/libicucore.A.dylib
0x93ca1000 - 0x93d51fff edu.mit.Kerberos 6.0.12 (6.0.12) <3dd13466876a8fe4549cfc1354233ec3> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x94249000 - 0x9424dfff libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x945a2000 - 0x945cdfe7 libauto.dylib ??? (???) <42d8422dc23a18071869fdf7b5d8fab5> /usr/lib/libauto.dylib
0x94f20000 - 0x9507fff3 libSystem.B.dylib ??? (???) <4899376234e55593b22fc370935f8cdf> /usr/lib/libSystem.B.dylib
0x958e1000 - 0x958efffd libz.1.dylib ??? (???) <5ddd8539ae2ebfd8e7cc1c57525385c7> /usr/lib/libz.1.dylib
0x96236000 - 0x96368fef com.apple.CoreFoundation 6.5.1 (476.10) <d5bed2688a5eea11a6dc3a3c5c17030e> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x96369000 - 0x963c6ffb libstdc++.6.dylib ??? (???) <04b812dcec670daa8b7d2852ab14be60> /usr/lib/libstdc++.6.dylib
0x969a1000 - 0x96b6cff7 com.apple.security 5.0.2 (33001) <0788969ffe7961153219be10786da436> /System/Library/Frameworks/Security.framework/Versions/A/Security
0xfffe8000 - 0xfffebfff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib

@Zaph - Can you please share your steps to roll back to previous SSH? Thanks

Just in case it helps, I did both SecUpd2008-002PPC and Safari31UpdPPC, am running Tiger on a G4 PB, and can ssh just fine. No bugs.

Here's my current take on the issue:

My ssh has the same problem as others here-I sent Apple a report. I already had Macports installed, but not Macports-openssh, so I decided to install that. It also does not work, although instead of immediately quitting & reporting a "bus error", it hangs (after first checking the installed RSA keys & adding the new key to the known_hosts file).

/opt/local/bin/ssh localhost
The authenticity of host 'localhost (::1)' can't be established.
RSA key fingerprint is blah-blah-blah.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'localhost' (RSA) to the list of known hosts.
(it just hangs here)

ssh localhost
Bus error

sudo ssh localhost
(prompts me for password, then hangs)

Any time it hangs, if I set CrashReporterPrefs to Developer, I get regular (~once per minute, but irregular) popups saying that the application "ssh-agent quit unexpectedly", with some further information I've sent to Apple.

I reinstalled the update (Security Update 2008-002 v1.0 (Leopard)) and restarted-nothing changed.

Of course, using putty for Windows through Parallels works-but I'd prefer a more elegant solution...

-Scot

downloaded todays security and safari update. my imac is now stuck in a constant restart loop. it gets to apple logo and black windmill then restarts constantly! I've flashed the pram, ran checks with disk utility using an old tiger disk, and also a full extensive hardware check(d on startup). I don't wanna lose my music games movies etc any tips guys? well scared!!

This thread is about getting the 'Bus error' when using ssh. Please don't hijack this thread.

Just an FYI - installed all updates (except the Leopard Graphics Update, which is still problematic for me) and am not having this problem:

-rwxr-xr-x 1 root wheel 574416 Feb 26 21:03 /usr/bin/ssh
-rwxr-xr-x 1 root wheel 691248 Feb 26 21:03 /usr/sbin/sshd
MD5 (/usr/bin/ssh) = 53be0ead4fa8e07461608cefd5474cce
MD5 (/usr/sbin/sshd) = 9957f27c3154dd0a45360e8f128db0d3

One thing that might help is:

ssh -v -v -v <hostname>

The three -vs turn on absolutely all debugging info, and might help track down what part of the startup or auth process is crashing.

I downloaded Mindterm (free for personal use), which is an SSH client written in Java: http://appgate.se/products/80_MindTerm/

You can run it like this: java -jar mindterm.jar

That doesn't help. You just get 'Bus error'.

Do you have a ~/.ssh ? If so, what are the permissions of the directory and files there? Also check /etc/ssh* - everything but the *key files should be world-readable.

mv'ing my .ssh directory to .ssh-bak was one of the first things I tried actually. It didn't help at all unfortunately. Permissions on the ssh config files in /etc look good. As for the contents of ssh_config, there are no options actually set. Everything in that file is a comment.

Are you sure? I've always done 'chmod 0700 ~/.ssh' and 'chmod 0600 ~/.ssh/*' and that worked just fine. Anyway, even if I rename .ssh to .ssh-bak the 'Bus error' remains, so permissions on .ssh don't seem to be related to the 'Bus error'.

It does seem ssh does not crash when I run 'sudo ssh'.