Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Terminal Error (SSH leads to Bus Error)

Heya,

Everytime I try to ssh on my client I get a Bus Error.
When I Su, and try again, it asks me for RSA authenticatin. I say yes, and then it hangs trying to connect - I assume it's tryign to connect.

The I get frustrated, I close the terminal, and I try again in su mode. It just hangs at that point.

Anyone know how to fix this?

Macbook (Intel Core Duo, Gen 1), Mac OS X (10.5.3)

Posted on Jun 6, 2008 7:41 AM

Reply
11 replies

Jun 6, 2008 10:07 AM in response to lazyrussian

That error would lead me to think there's a bug in your ssh client. Is this the stock ssh client that comes with OS X, or have you installed a different one via something like Fink or MacPorts?

You could run some debugging from ssh to see where things are hanging up. From your client, you could use the -v option which will give your some debugging information and may tell you who is hanging up. If that doesn't tell you anything, you can do some similar things on the remote side to the sshd daemon that is accepting your connection.

However, I'm still concerned about the bus error. Can you paste your connection attempt here, showing that error?

Jun 6, 2008 10:28 AM in response to glsmith

Heya,

thanks for the reply. I'm using the Terminal.app client.

Here's the output of my connection attempt:

swire-d169:~ Arthur$ ssh -v jlab.org
Bus error
swire-d169:~ Arthur$ su
Password:
sh-3.2# ssh -v jlab.org
OpenSSH_4.7p1, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to jlab.org [129.57.48.43] port 22.
debug1: Connection established.
debug1: permanently setuid: 0/0
debug1: identity file /var/root/.ssh/identity type -1
debug1: identity file /var/root/.ssh/id_rsa type -1
debug1: identity file /var/root/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.7.1p2
debug1: match: OpenSSH_3.7.1p2 pat OpenSSH_3.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7
debug1: SSH2 MSGKEXINIT sent
debug1: SSH2 MSGKEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2 MSG_KEX_DH_GEXREQUEST(1024<1024<8192) sent
debug1: expecting SSH2 MSG_KEX_DH_GEXGROUP
debug1: SSH2 MSG_KEX_DH_GEXINIT sent
debug1: expecting SSH2 MSG_KEX_DH_GEXREPLY
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for jlab.org has changed,
and the key for the according IP address 129.57.48.43
is unchanged. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
Offending key for IP in /var/root/.ssh/known_hosts:2
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
d3:e0:d6:84:02:24:66:9c:b0:28:7e:24:3e:1f:d4:46.
Please contact your system administrator.
Add correct host key in /var/root/.ssh/known_hosts to get rid of this message.
Offending key in /var/root/.ssh/known_hosts:1
RSA host key for jlab.org has changed and you have requested strict checking.
Host key verification failed.

Jun 6, 2008 10:45 AM in response to lazyrussian

Hmm, maybe it's the shell that's the problem. Can you try this:

prompt% sh

(this just runs a new shell within the same Terminal window)

sh-prompt% ssh -v jlab.org

Does this also give a bus error?

As root, everything looks fine with ssh and the remote connection, aside from the fact that you have some authentication/authorization issues. Before you can debug that, though, we need to figure out why you can't run ssh as your user...

Jun 6, 2008 11:41 AM in response to lazyrussian

Ok, found this thread:

http://discussions.apple.com/thread.jspa?messageID=6859298

It's long, but worth reading through. Any chance you installed Rogue Amoeba's Instant Hijack? If so, then run

sudo /usr/local/hermes/bin/hermesctl unload

and/or check RA's site for the correct patches (if any, I have zero experience with that software).

Message was edited by: glsmith

Terminal Error (SSH leads to Bus Error)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.