ssh not working after Daylight Savings, Java, and security updates

Question

Level 1

0 points

ssh not working after Daylight Savings, Java, and security updates

I woke up this morning to see that there were 3 software updates available, and so I installed all three. No problems with the install, and after restarting everything appeared to be working fine. Then I opened the Terminal and tried to ssh to another machine and got a "Segmentation Fault" error.

This seg fault happens with both terminal and X11, and over both wireless and ethernet connections. Pings still work, as do other UNIX TCP utilities (I tried telnet and ftp), so the problem seems to affect just SSH.

Has anyone else experienced this problem?

Macbook core2duo 2Ghz, Mac OS X (10.4.8)

Posted on Feb 16, 2007 11:38 AM

Reply

Answer 1

Feb 17, 2007 11:15 AM in response to scottj75

I have the same problem. Anybody has an answer to solve that?

Here the verbose output from ssh (I deleted all the computer names etc.):

debug1: Reading configuration data /etc/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to [] port 22.
debug1: Connection established.
debug1: identity file /Users/<user>/.ssh/identity type -1
debug1: identity file /Users/<user>/.ssh/id_rsa type -1
debug1: identity file /Users/<user>/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.8.1p1 Debian-8.sarge.4
debug1: match: OpenSSH_3.8.1p1 Debian-8.sarge.4 pat OpenSSH_3.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.2
debug2: fd 3 setting O_NONBLOCK

Robert
Segmentation fault

Mac OS X (10.4.8)

Reply

Answer 2

Feb 17, 2007 4:12 PM in response to scottj75

I tried, but I don't seem to have that problem.

Reply

Answer 3

scottj75 Author

Level 1

0 points

Feb 17, 2007 9:11 PM in response to spingineer

Looking around the web, I've seen that this problem has cropped up before this update. I've seen people complain that it happened to them after the airport update in early February. But it definitely hit me after the Feb 15 updates.

See http://forums.macosxhints.com/showthread.php?t=67983

spingineer, is your Mac Mini a PPC or Intel chip?

What's strage is that it seems to be sporadic, and not affecting everyone after every single update. I just hope Apple releases a fix soon, because this is a huge bug for anyone who does remote computing.

Reply

Answer 4

Feb 18, 2007 7:35 AM in response to scottj75

spingineer, is your Mac Mini a PPC or Intel chip?

My Mac Mini is an Intel, single core. In fact, I have to VPN into the office, and SSH various servers, and all without a problem. I've also been able to SSH to other routers and firewalls too.

Reply

Answer 5

Feb 18, 2007 8:19 AM in response to scottj75

I have been reading other posts on several other forms that describe different problems associated with the install of these updates.

I am NOT going to install the updates now.

If you find out, please let this forum know, and others if you have the time, what the heck the problem is.

Reply

Answer 6

Feb 18, 2007 11:00 AM in response to alveolari

I have no problem, but I'm using protocol 1.99 to connect to
Redhat. Can you force it to use protocol 1 (ssh -1)?

I think you should file a bug report and send the coredump
to Apple.

-Phil

Reply

Answer 7

Feb 20, 2007 10:58 AM in response to scottj75

The easiest fix for now is to install ssh from Fink.

This is an unacceptable error on Apple's part, to break a critical component of the operating system. What is the best way to alert them to this? Would calling AppleCare accomplish anything? I suspect the staff at AppleCare don't know what ssh is or why it might be critical.

-Eric

Reply

Answer 8

scottj75 Author

Level 1

0 points

Feb 20, 2007 4:14 PM in response to Eric Salathe

Well, I just tried this on a co-worker's computer (a Macbook CoreDuo with same OS version) who just installed the 3 Feb 15th updates, and his SSH works fine.

I've also found another thread where somebody had the same problem after upgrading to 10.4.7.

http://forums.macrumors.com/archive/index.php/t-213307.html

One anecdotal observation I see so far is that the problem with SSH seems to hit people who have the Developer Tools installed (as I do). Would that make any sense?

-Scott

Reply

Answer 9

Feb 26, 2007 2:41 PM in response to Eric Salathe

OK, here's the problem and fix.

Something gets messed up with Kerberos during some Apple patches. This is clearly established by the vast user experiences posted around the web related both the the latest (Feb 2007 10.4.8) updates and earlier updates. When Kerberos is messed up, various communications are broken. There are specific reports regarding ssh and afp.

The fix is to go back to an earlier version of the affected software that works correctly. In this case, I went back to the 10.4.8 Combo Updater <http://www.apple.com/support/downloads/macosx1048comboupdateintel.html> and used Pacifist <http://www.charlessoft.com/> to install just the Kerberos.framework (/System/Library/Frameworks/). Doing this fixed segmentation faulting both in ssh and afp.

Elsewhere, I have seen the suggestion to also reinstall /System/Library/CoreServices/{Kerberos.app,KerberosAgent.app}. However, it seems more likely that the framework is at fault and those apps are calling the framework.

So, to be clear: ssh worked fine on my MacBook Pro until the last security update. After which, it terminated with segmentation fault. I reinstalled Kerberos.framework from the 10.4.8 Combo Updater, which fixed ssh. (As well as a lingering afp issue from earlier updates.) Note also that non-Apple builds of ssh (MacPorts or Fink), which do not use Kerberos.framework, work fine.

-Eric

MacBook Pro Mac OS X (10.4.8)

Reply

Answer 10

scottj75 Author

Level 1

0 points

Feb 27, 2007 2:26 AM in response to Eric Salathe

Thanks for the great post, Eric.

Followed your instructions and the problem is fixed.

cheers,
Scott

Reply

Answer 11

Feb 27, 2007 8:05 AM in response to Eric Salathe

Thank you, Eric. Thanks to your sleuthing I'm skipping applying the patches to my iMac, saving myself a ton of trouble. I sure appreciate it.

-Phil

Reply

Answer 12

DLz

Level 1

15 points

Mar 5, 2007 11:50 AM in response to scottj75

Thanks Eric for providing the fix. I'm still waiting for the Combo updater to download, but I'm sure the fix will work, since this is the SECOND TIME I'm
having to do this, the first being back when I went to 10.4.7. It's pretty disappointing that this bug is back.

D.

Reply

Answer 13

Sorte

Level 1

0 points

Mar 28, 2007 4:30 PM in response to Eric Salathe

I'm running 10.4.9 currently and had this same ssh segmentation fault issue arise. I've attempted to follow the directions posted by Eric, but I fail to see a Kerberos.framework component in the 10.4.8 update. Am I doing something wrong?

Reply

Answer 14

BDAqua

Level 10

250,409 points

Mar 28, 2007 11:45 PM in response to Sorte

Did you get the BIG Combo update?

Reply

Answer 15

Sorte

Level 1

0 points

Mar 29, 2007 8:25 AM in response to BDAqua

Well, I followed the link provided in the post above (Mac OS X 10.4.8 Combo Update (Intel) ). Is there another one? I've searched the Apple website and only found this one...

Thanks for the reply.

Reply