Posts:
33
From:
The Netherlands
Registered:
May 5, 2007
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 7:26 PM
in response to: sabrom
|
|
|
Are you sure? I've always done 'chmod 0700 ~/.ssh' and 'chmod 0600 ~/.ssh/*' and that worked just fine. Anyway, even if I rename .ssh to .ssh-bak the 'Bus error' remains, so permissions on .ssh don't seem to be related to the 'Bus error'.
It does seem ssh does not crash when I run 'sudo ssh'.
MacBook 13,3" 2.0 GHz 120 GB HD 2 GB RAM Black
Mac OS X (10.5.2)
|
|
Posts:
7
From:
Australia
Registered:
Dec 19, 2007
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 7:27 PM
in response to: hirschnase
|
|
|
I'd rather not detail the process - if you should know, you'd already know. It involved copying the old file to a backup and then replacing it with one from a TimeMachine backup, but it needs to be done as root, and will need to be reversed again once Apple releases a fix (hence my hesitation).
iMac Core Duo 17"
Mac OS X (10.5.1)
|
|
Posts:
33
From:
The Netherlands
Registered:
May 5, 2007
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 7:30 PM
in response to: Zaph
|
|
|
Why would it need to be reversed once Apple releases a fix? That fix would just overwrite the ssh binary again, wouldn't it?
MacBook 13,3" 2.0 GHz 120 GB HD 2 GB RAM Black
Mac OS X (10.5.2)
|
|
Posts:
8
Registered:
Feb 27, 2006
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 7:32 PM
in response to: breun
|
|
|
I second those permissions on ~/.ssh and ~/.ssh/*. Although, it's quite possible that sabrom was talking about the ssh related files in /etc.
Mac Book Pro 2.13
Mac OS X (10.5.2)
2 GB Ram 100 GB 7200 RPM
|
|
Posts:
8
Registered:
Jan 16, 2005
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 7:39 PM
in response to: hirschnase
|
|
Helpful
|
|
|
Ok...this is definitely not best practice but as I literally can't work without ssh (and MindTerm just feels really clunky) I've found a functional workaround for now. Basically ssh seems work fine when run as root (not sudo but really root).
-enable root if you haven't already
-in Terminal "sudo su -" to become root with root's environment -- you'll have to put in your users password of course (and have to be an admin as well to use that password for sudo)
-as root, if you need any bash shortcuts just "ln -s /Users/<username>/.profile .profile" (replace <username> with your actual username....this is just making a symlink in case you're not sure)
-as root, if you need your ssh private key/known public keys (as I'm guessing most do), then "ln -s /Users/<username>/.ssh .ssh"
-Log out from root and then log back in so bash rereads those files
You're now good to go (or at least I am  ).
I won't be doing anything else in the shell as root but running ssh so hopefully won't do anything too stupid.
Message was edited by: Andrew and Jamie Miller
|
|
Posts:
7
From:
SF
Registered:
Mar 18, 2008
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 7:46 PM
in response to: JasonPro
|
|
|
Sorry - yes, I was just talking about the ones in /etc.
Some brave soul want to try a dtruss sudo <user> ssh to see what the last system call is before the bus error? (Will this even work?)
MB, MBP
Mac OS X (10.5.2)
|
|
Posts:
6
From:
Anchorage, Alaska
Registered:
Jan 16, 2008
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 7:51 PM
in response to: Andrew and Jami...
|
|
|
Makes me wonder if making a new dummy user after the update will work around the problems. Or is it root only that works? If so, sounds like a permissions problem.
Somebody (experiencing the problem) care to create a new user in System Prefs, su to that user, and see if they can SSH?
Mac Pro
Mac OS X (10.5.1)
|
|
Posts:
7
From:
Australia
Registered:
Dec 19, 2007
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 7:55 PM
in response to: breun
|
|
|
breun - it may do, but I'd rather put things back exactly as they were before applying the next update.
iMac Core Duo 17"
Mac OS X (10.5.1)
|
|
Posts:
9
From:
Australia
Registered:
Nov 12, 2007
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 7:55 PM
in response to: elliottcable
|
|
|
Still fails with a brand new user account.
MacBook Pro 17"
Mac OS X (10.5.2)
|
|
Posts:
1
From:
Shanghai, China
Registered:
Mar 18, 2008
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 8:20 PM
in response to: Jason π
|
|
|
Do you by the way have a customized /etc/ssh_config ?
MacBook Pro
Mac OS X (10.5.2)
MBP 2.4G, 2G, 160G
|
|
Posts:
8
Registered:
Jan 16, 2005
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 8:39 PM
in response to: leafy7382
|
|
|
Same "Bus Error" after creating a new admin user and no, no customizations to my ssh_config.
The permissions look fine as far as I can tell - 755 (everyone can execute and read, only root can write).
-rwxr-xr-x 1 root wheel 574416 Feb 27 00:03 /usr/bin/ssh
|
|
Posts:
4
Registered:
Oct 1, 2006
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 11:27 PM
in response to: hirschnase
|
|
Solved
|
|
|
Have you installed Rogue Amoeba's Instant Hijack?
If so, try:
sudo /usr/local/hermes/bin/hermesctl unload
then see if ssh works again.
|
|
Posts:
3
From:
Fremont, CA
Registered:
Mar 19, 2008
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 11:31 PM
in response to: Peter Gryphon
|
|
|
Bingo -- this fixes the issue for me.
Mac OS X (10.5.2)
|
|
Posts:
9
From:
Australia
Registered:
Nov 12, 2007
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 18, 2008 11:39 PM
in response to: Peter Gryphon
|
|
|
Thank you! That's it. SSH works when Instant Hijack is stopped.
I have removed Instant Hijack and will wait until Rogue Amoeba releases a fix. I don't need Instant Hijack more than SSH
MacBook Pro 17"
Mac OS X (10.5.2)
|
|
Posts:
10
From:
Phoenix
Registered:
Jan 14, 2008
|
|
|
|
Re: After Security Update today: "Bus error" when starting "ssh" client
Posted:
Mar 19, 2008 12:00 AM
in response to: Peter Gryphon
|
|
|
Thank you very much. This fixed the problem for me.
MacBook Pro 2.4Ghz Santa Rosa
Mac OS X (10.5.1)
|
|
|
