Benches macOS

15

Security update 2008-002 breaks ssh

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Since applying today's security update 2008-002, all my 'secure' services (the s* commands) cause a bus error. For example:

$ ssh localhost

Bus error

Wow.

15 replies

Sign in or join Beachball Help to reply.

  1. 0

    the.ftf

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    roger that, same here.

  2. 0

    Monty1945

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Greetings,

    Strange - SSH is Ok here, after the security update, and Safari. Odd

    Cheers,

    M.


    **********

  3. 0

    hirschnase

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    same thing here 😟

  4. 0

    steuben

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    An addendum: after putting files from a pre-patch system back onto the patched system (scp, ssh, ssh-agent) the ssh-agent no longer stores keys and RSA authentication of hosts is broken.

    I'm guessing the Keychain was modified in the security patch.

  5. 0

    steuben

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Please ignore my comment about ssh-agent. I neglected to return files to ~/.ssh after I did some testing. ssh-agent, using the binaries before the patch, works fine.

  6. 0

    ichdertom

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Same Problem here.

    Executing the command "ssh" causes a "Bus error"

  7. 0

    Chris D Searle

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Are these binaries available for download from apple anywhere (or other site)? Am sitting up in the mountains on mobile internet with limited access - but - getting at least the ssh binary to run would be a real help (ssh-agent etc I can work around- but plain ssh to a server is a must).

  8. 0

    flowb33

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Same problem here. Locked out of my servers now. I've deleted ~/.ssh/known_hosts and my keychain entries for these servers. Neither of these fixed the problem.

  9. 0

    jmcollis

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yes. I'm having the same issues. I had been using SSHKeychain that changes the default path for the SSH
    AUTHSOCK environment variable. I've tested without this and also with this on the system default and this doesn't fix the issue. Neither does moving sideways my .ssh directory.

    This is pretty serious for me as I can't login to my company servers. I'm off to find a backup now.

  10. 0

    E.O. Stinson

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Same problem.

    Process: ssh [574]

    Path: /usr/bin/ssh

    Identifier: ssh

    Version: ??? (???)

    Code Type: X86 (Native)

    Parent Process: bash [541]

    Date/Time: 2008-03-18 16:03:04.198 -0700

    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: 0xbffff878 esp: 0xbffff850

    ss: 0x0000001f efl: 0x00010286 eip: 0x0004c4e7 cs: 0x00000017

    ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

    cr2: 0x00001014

    Binary Images:

    0x5b6de000 - 0x5b71bfef +ssh ??? (???) <38f6d3ec24f0b372e64c12b15bb319d4> /usr/bin/ssh

    0x8fe00000 - 0x8fe2da53 dyld 96.2 (???) <7af47d3b00b2268947563c7fa8c59a07> /usr/lib/dyld

    0x902dd000 - 0x902ebffd libz.1.dylib ??? (???) <5ddd8539ae2ebfd8e7cc1c57525385c7> /usr/lib/libz.1.dylib

    0x9038c000 - 0x903e9ffb libstdc++.6.dylib ??? (???) <04b812dcec670daa8b7d2852ab14be60> /usr/lib/libstdc++.6.dylib

    0x903ea000 - 0x9049afff edu.mit.Kerberos 6.0.12 (6.0.12) <3dd13466876a8fe4549cfc1354233ec3> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos

    0x9049b000 - 0x904c6fe7 libauto.dylib ??? (???) <42d8422dc23a18071869fdf7b5d8fab5> /usr/lib/libauto.dylib

    0x90a09000 - 0x90b41ff7 libicucore.A.dylib ??? (???) <afcea652ff2ec36885b2c81c57d06d4c> /usr/lib/libicucore.A.dylib

    0x90b42000 - 0x90d0dff7 com.apple.security 5.0.2 (33001) <0788969ffe7961153219be10786da436> /System/Library/Frameworks/Security.framework/Versions/A/Security

    0x91b4b000 - 0x91b52ffe libbsm.dylib ??? (???) <d25c63378a5029648ffd4b4669be31bf> /usr/lib/libbsm.dylib

    0x921da000 - 0x9228cffb libcrypto.0.9.7.dylib ??? (???) <330b0e48e67faffc8c22dfc069ca7a47> /usr/lib/libcrypto.0.9.7.dylib

    0x92bd8000 - 0x92bf6fff libresolv.9.dylib ??? (???) <0629b6dcd71f4aac6a891cbe26253e85> /usr/lib/libresolv.9.dylib

    0x92f7f000 - 0x92f86fe9 libgcc_s.1.dylib ??? (???) <f53c808e87d1184c0f9df63aef53ce0b> /usr/lib/libgcc_s.1.dylib

    0x940e9000 - 0x941c8fff libobjc.A.dylib ??? (???) <a53206274b6c2d42691f677863f379ae> /usr/lib/libobjc.A.dylib

    0x94466000 - 0x9446afff libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib

    0x954c9000 - 0x955fbfef com.apple.CoreFoundation 6.5.1 (476.10) <d5bed2688a5eea11a6dc3a3c5c17030e> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation

    0x95699000 - 0x957f8ff3 libSystem.B.dylib ??? (???) <4899376234e55593b22fc370935f8cdf> /usr/lib/libSystem.B.dylib

    0xfffe8000 - 0xfffebfff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib

    0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib

  11. 0

    Nectar

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    What is the command line you are using? Perhaps running the following commands will help reveal the problem:

    (a) ssh

    (b) ssh -vvvv <target host>

    Running (a) will help determine whether the ssh binary is completely hosed. Running (b) might reveal at what stage ssh is crashing, and whether it is due to using certain key types or authentication methods.

  12. 0

    ichdertom

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    a)

    :~ ichdertom$ ssh

    Bus error

    b)

    :~ ichdertom$ ssh -vvvv pageya.com

    Bus error

  13. 0

    E.O. Stinson

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I too managed to get this working by copying over old files.

    If you're up for a challenge, you can pull the SSH binaries out of the Mac OS X 10.5.2 combo update, available here:
    http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx1052comboupdate .html.

    *Note that the downside is that the combo update is like 343MB, which may be untenable over wireless/mobile. If you've got MacPorts installed, you might try "port -v install openssh" and then just use /opt/local/bin/ssh until Apple gets their act together.*

    Steps:

    1. Download the update DMG.

    2. Download OpenUp, for pulling the file out of the installer package.

    3. Open the update DMG, right-click on the installer package, and choose Show Package Contents.

    4. Drag the Archive.pax.gz file to a new folder on your Desktop, and use OpenUp to extract it.

    5. Browse to the "Archive_X/usr/bin" folder and grab the ssh binaries:

    ssh

    scp

    sftp

    ssh-add

    ssh-agent

    ssh-keygen

    ssh-keyscan

    6. Drag these files to your usr/bin directory (possibly copying the originals first) and voila.

    *Some other thoughts.*

    Running SSH inside gdb gives a standard segfault kind of error:

    Program received signal EXC
    BADACCESS, Could not access memory.

    Reason: KERN
    PROTECTIONFAILURE at address: 0x00001014

    Probably somebody just compiled SSH against the wrong libraries, so it should be an easy fix. Here's hoping.

    Message was edited by: E.O. Stinson

    Message was edited by: E.O. Stinson

  14. 0

    Chris D Searle

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I cheated - I threw the fink ssh binaries on temporarily (these work OK for me right now) - as I needed an urgent fix.

    I've also thrown this up on apple's radar (id: 5806081) - I have no idea if this will have any effect - but at least it felt like I was doing something 🙂

  15. 0

    Courcoul

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Well, just patched the new MBP with SU 2008-002 with all the customary precautions I was used to in the Tiger world (repair disk, repair permissions, patch, reboot, repair permissions again). Tried ssh'ing to all my servers after seeing this thread and had no errors or problems connecting every time.