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

No problem here. Running 10.5.2 with the latest updates. I can ssh from my MBP to my iMac and back. I can also ssh to my linux server and back. No problems in either direction (for which I'm relieved).

This isn't happening for me.

I've installed the security update and safari 3.1 in the last three hours and can ssh in to my servers via the command line.

It's MacPorts, not Darwin Ports.

Works for me too. mbp core duo to mac mini. SFTP also is working

I'm not familiar with those repositories, but it seems Darwin Ports also exists: http://openssh.darwinports.com/

If someone could post the location of 'CrashReporterPrefs' maybe I can also generate a crash report. Spotlight isn't finding anything.

Got the error on one of three machines (iMac). SSH works on both MacPro and MBP with security update and Safari update.

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

Date/Time: 2008-03-18 20:42:02.732 -0400
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: 0xbffffa98 esp: 0xbffffa70
ss: 0x0000001f efl: 0x00010282 eip: 0x0004c4e7 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00001014

Binary Images:
0x60e37000 - 0x60e74fef +ssh ??? (???) <38f6d3ec24f0b372e64c12b15bb319d4> /usr/bin/ssh
0x8fe00000 - 0x8fe2da53 dyld 96.2 (???) <7af47d3b00b2268947563c7fa8c59a07> /usr/lib/dyld
0x9338f000 - 0x934eeff3 libSystem.B.dylib ??? (???) <4899376234e55593b22fc370935f8cdf> /usr/lib/libSystem.B.dylib
0x934ef000 - 0x934f3fff libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x934f9000 - 0x935abffb libcrypto.0.9.7.dylib ??? (???) <330b0e48e67faffc8c22dfc069ca7a47> /usr/lib/libcrypto.0.9.7.dylib
0x93674000 - 0x936d1ffb libstdc++.6.dylib ??? (???) <04b812dcec670daa8b7d2852ab14be60> /usr/lib/libstdc++.6.dylib
0x9371a000 - 0x93738fff libresolv.9.dylib ??? (???) <0629b6dcd71f4aac6a891cbe26253e85> /usr/lib/libresolv.9.dylib
0x93739000 - 0x937e9fff edu.mit.Kerberos 6.0.12 (6.0.12) <3dd13466876a8fe4549cfc1354233ec3> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x94000000 - 0x940dffff libobjc.A.dylib ??? (???) <a53206274b6c2d42691f677863f379ae> /usr/lib/libobjc.A.dylib
0x947b2000 - 0x947b9fe9 libgcc_s.1.dylib ??? (???) <f53c808e87d1184c0f9df63aef53ce0b> /usr/lib/libgcc_s.1.dylib
0x947ba000 - 0x94985ff7 com.apple.security 5.0.2 (33001) <0788969ffe7961153219be10786da436> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x94f38000 - 0x94f3fffe libbsm.dylib ??? (???) <d25c63378a5029648ffd4b4669be31bf> /usr/lib/libbsm.dylib
0x9531c000 - 0x95347fe7 libauto.dylib ??? (???) <42d8422dc23a18071869fdf7b5d8fab5> /usr/lib/libauto.dylib
0x95367000 - 0x9549fff7 libicucore.A.dylib ??? (???) <afcea652ff2ec36885b2c81c57d06d4c> /usr/lib/libicucore.A.dylib
0x96660000 - 0x9666effd libz.1.dylib ??? (???) <5ddd8539ae2ebfd8e7cc1c57525385c7> /usr/lib/libz.1.dylib
0x96d2b000 - 0x96e5dfef com.apple.CoreFoundation 6.5.1 (476.10) <d5bed2688a5eea11a6dc3a3c5c17030e> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0xfffe8000 - 0xfffebfff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib

If you did not explicitly install the Developer Tools I don't think you have the app, since my copy of the app is located in /Developer/Applications/Utilities. There may be a terminal command to change the crash reporting mode but I don't know it.

Could someone please check the modification time of ssh to see if Apple modded it and broke it or if the segfault is due to a resource that they disallowed it access to? Maybe we can fix this ourselves for now.

Its broken here also after the update with the same bus error.

It's a new binary. From /usr/bin/:

New: -rwxr-xr-x 1 root wheel 574416 Feb 27 00:03 ssh

Old: -rwxr-xr-x 1 root wheel 545472 Sep 24 01:11 ssh

From the notes for the 2008-002 security update: "(...) This update addresses the issue by updating OpenSSH to version 4.7. Further information is available via the OpenSSH website at http://www.openssh.org/txt/release-4.7"

So yes, the update installed a new version of OpenSSH.

ah. well that's a bummer, it'll probably take longer to fix then. 😟. however doesn't that mean we could simply replace it with the older version of openssh? I'm assuming there are no significant resource changes..

go here and d/l the newest update: http://www.apple.com/support/downloads/

*Security Update 2008-002 v1.0 (Leopard)*

I replaced the ssh binary with the one before the update (from yesterday) and SSH does now work as expected from the command line.