Please help. ssh seg faults

Question

Level 1

0 points

Please help. ssh seg faults

Hi,

SSH is seg faulting ever since I upgraded to 10.4.8. If I force version 1 it is ok, but that's not a solution. Also, Keychain Access.app is seg faulting.

Please, if you can, help me figure this out.

Thanks,
Gabe

mac book pro, Mac OS X (10.4.8)

Posted on Oct 4, 2006 11:37 AM

Reply

Answer 1

warnes

Level 1

0 points

Dec 12, 2006 2:45 PM in response to sibs

I'm having the same issue, but can add some additional details.

The ssh binary crashes with the message "segmentation fault" when I attemtp to connect to a machine running a different ssh implementation, but connects without problems when I connect to another Mac.

Here's the output of
ssh -v -v <solaris machine>

OpenSSH_4.2p1, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /etc/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to machine.sub.domain.tld
[172.18.161.21] port 22.
debug1: Connection established.
debug1: identity file /Users/user/.ssh/identity type -1
debug1: identity file /Users/user/.ssh/id_rsa type -1
debug2: keytype_fromname: unknown key type '-----BEGIN'
debug2: keytype_fromname: unknown key type '-----END'
debug1: identity file /Users/user/.ssh/id_dsa type 2
debug1: sshexchangeidentification: sshd[16072]: WARNING: DNS lookup failed for
"172.17.48.48".
debug1: Remote protocol version 1.99, remote software version 3.2.5 SSH Secure S
**** (non-commercial)
debug1: no match: 3.2.5 SSH Secure Shell (non-commercial)
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.2
debug2: fd 3 setting O_NONBLOCK
Segmentation fault
[macbook:~] user%

Reply

Answer 2

Ethanee

Level 2

350 points

Dec 12, 2006 8:47 PM in response to sibs

Also, Keychain Access.app is seg faulting.

Have you tried clearing (i.e. removing) com.apple.keychainaccess.plist?

Reply

Answer 3

Dec 13, 2006 11:25 PM in response to sibs

and for the ssh, open a terminal and remove ".ssh" directory at your home directory. Hope this helps...

Reply

Answer 4

sibs Author

Level 1

0 points

Mar 12, 2007 9:37 PM in response to hsaybasili

It's been a while since I dealt with this, but the base issue was with the Kerberos libraries. Simple things, like nuking ~/.ssh, didn't help.

There was one solution - basically to copy the original kerberos libraries off the install cd - but the system remained flakey. In the end, I used the shotgun approach and just reinstalled everything from scratch. As a dyed in the wool Unix user, this irks me to no end. OSX sure as **** ain't no Unix if we can't get under the hood and figure out why it's broken. Reinstalling the OS is Microsoft kind of "solution."

Anyway, the system (Intel Core Duo, 2ghz MPB) had hardware troubles to boot. Bad video card (started freezing on boot %50 of the time). Ultimately it ended up smoking it's power supply (literally let the magic smoke out).

I swapped it for a Intel 2 Core Duo version and so far things are much better. The thing is quieter, cooler, faster, more stable (no problems so far). Sure, I've broken some things software wise, but I've been able to fix them. So far so good.

Reply