Apple Event: May 7th at 7 am PT

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

Level 1

0 points

SSH/SFTP fails silently on OSX 10.8.2 - ssh-agent issue

I'm trying to login to a remote machine with SSH or SFTP.

when I try `ssh u-indgo@ssh1.eu1.frbit.com` the CLI just won't respond. I get an empty new line, in which I can type characters, but nothing more.

When I try to connect with `SFTP` using the same credentials (I use `Transmit` as my SFTP client) it just hangs forever and doesn't connect.

No errors. No response.

The problem isn't specific to `frbit.com` and persists with other IP's as well.

running with the -vv flag I got the following output:

debug1: Reading configuration data /Users/matanya/.ssh/config

debug1: Reading configuration data /usr/local/Cellar/openssh/6.1p1/etc/ssh_config

debug2: ssh_connect: needpriv 0

debug1: Connecting to ssh1.eu1.frbit.com [46.137.57.195] port 22.

debug2: fd 3 setting O_NONBLOCK

debug1: fd 3 clearing O_NONBLOCK

debug1: Connection established.

debug1: identity file /Users/matanya/.ssh/id_rsa type 1

debug1: identity file /Users/matanya/.ssh/id_rsa-cert type -1

debug1: identity file /Users/matanya/.ssh/id_dsa type 2

debug1: identity file /Users/matanya/.ssh/id_dsa-cert type -1

debug1: identity file /Users/matanya/.ssh/id_ecdsa type -1

debug1: identity file /Users/matanya/.ssh/id_ecdsa-cert type -1

debug1: Remote protocol version 2.0, remote software version OpenSSH_5.5p1

debug1: match: OpenSSH_5.5p1 pat OpenSSH_5*

debug1: Enabling compatibility mode for protocol 2.0

debug1: Local version string SSH-2.0-OpenSSH_6.1

debug2: fd 3 setting O_NONBLOCK

debug1: SSH2_MSG_KEXINIT sent

debug1: SSH2_MSG_KEXINIT received

debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-e xchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,di ffie-hellman-group1-sha1

debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-dss-cert-v00@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-dss

debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blow fish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se

debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96

debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib

debug2: kex_parse_kexinit:

debug2: kex_parse_kexinit: first_kex_follows 0

debug2: kex_parse_kexinit: reserved 0

debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie- hellman-group14-sha1,diffie-hellman-group1-sha1

debug2: kex_parse_kexinit: ssh-rsa,ssh-dss

debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blow fish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se

debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96

debug2: kex_parse_kexinit: none,zlib@openssh.com

debug2: kex_parse_kexinit:

debug2: kex_parse_kexinit: first_kex_follows 0

debug2: kex_parse_kexinit: reserved 0

debug2: mac_setup: found hmac-md5

debug1: kex: server->client aes128-ctr hmac-md5 none

debug2: mac_setup: found hmac-md5

debug1: kex: client->server aes128-ctr hmac-md5 none

debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent

debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP

debug2: dh_gen_key: priv key bits set: 140/256

debug2: bits set: 543/1024

debug1: SSH2_MSG_KEX_DH_GEX_INIT sent

debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY

debug1: Server host key: RSA 31:4c:71:e0:56:14:04:0d:c7:b2:6c:fc:8a:42:33:2e

debug1: Host 'ssh1.eu1.frbit.com' is known and matches the RSA host key.

debug1: Found key in /Users/matanya/.ssh/known_hosts:2

debug2: bits set: 513/1024

debug1: ssh_rsa_verify: signature correct

debug2: kex_derive_keys

debug2: set_newkeys: mode 1

debug1: SSH2_MSG_NEWKEYS sent

debug1: expecting SSH2_MSG_NEWKEYS

debug2: set_newkeys: mode 0

debug1: SSH2_MSG_NEWKEYS received

debug1: Roaming not allowed by server

debug1: SSH2_MSG_SERVICE_REQUEST sent

debug2: service_accept: ssh-userauth

debug1: SSH2_MSG_SERVICE_ACCEPT received

UPDATE: going through `system.log` I found the following:

Mar 6 10:28:17 matanyas-imac com.apple.launchd.peruser.501[235] (org.openbsd.ssh-agent[574]): Exited with code: 1

Mar 6 10:28:17 matanyas-imac com.apple.launchd.peruser.501[235] (org.openbsd.ssh-agent): Throttling respawn: Will start in 10 seconds

Mar 6 10:28:27 matanyas-imac com.apple.launchd.peruser.501[235] (org.openbsd.ssh-agent[575]): Exited with code: 1

Mar 6 10:28:27 matanyas-imac com.apple.launchd.peruser.501[235] (org.openbsd.ssh-agent): Throttling respawn: Will start in 10 seconds

What does `Code 1` stand for?

UPDATE: Following @Eir Nym advice, I found the file that `launchd` has problems with at `System/Library/LaunchAgents/org.openbsd.ssh-agent.plist`:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>Label</key>

<string>org.openbsd.ssh-agent</string>

<key>ProgramArguments</key>

<array>

<string>/usr/bin/ssh-agent</string>

</array>

<key>ServiceIPC</key>

<true/>

<key>Sockets</key>

<dict>

<key>Listeners</key>

<dict>

<key>SecureSocketWithKey</key>

</dict>

<key>EnableTransactions</key>

<true/>

</dict>

</plist>

When I run `/usr/bin/ssh-agent` I get:

SSH_AUTH_SOCK=/var/folders/pg/1g6_hnwx47bgqv5vcm1lq18h0000gn/T//ssh-01WuaHF32Sl V/agent.2145; export SSH_AUTH_SOCK;

SSH_AGENT_PID=2146; export SSH_AGENT_PID;

echo Agent pid 2146;

as for the `-l` flag (`<string>-l</string>`) there is no such flag on my version of `ssh-agent`. Outputs:

ssh-agent: illegal option -- l

SSH version: OpenSSH_5.8p2, OpenSSL 0.9.8r 8 Feb 2011

iMac, OS X Mountain Lion (10.8.2)

Posted on Mar 8, 2013 3:02 AM

25 replies

matfish2 Author

Level 1

0 points

Mar 9, 2013 11:25 AM in response to Linc Davis

Not sure what is the difference between the shell and the console.

Can you please be more specific? I have very little exprience with the CLI.

Linc Davis

Level 10

209,547 points

Mar 9, 2013 11:47 AM in response to matfish2

I mean a graphical login, not a shell login with su.

matfish2 Author

Level 1

0 points

Mar 9, 2013 11:55 AM in response to Linc Davis

No. Even when I login on system startup via the graphical interface as root, I still don't get ssh-agent in the Activity Monitor.

Linc Davis

Level 10

209,547 points

Mar 9, 2013 11:59 AM in response to matfish2

Don't log in as root. That's very dangerous, and anyway the root user can't have launchd agents, and ssh-agent is an agent. Log in as another standard user. Use the guest account if you don't already have one.

Mar 9, 2013 12:07 PM in response to matfish2

My .ssh directories are all 700. Might want to try setting them that way

Nevermind set my to 755 and it still works

matfish2 Author

Level 1

0 points

Mar 9, 2013 12:22 PM in response to Linc Davis

Logged as Guest. Still nothing. only when I explicitly run it I see it in the Activity Monitor.

As I mentioned in my OP it seems to be called by launchd with the -l flag, which doesn't even exist on my ssh-agent installation.

etresoft

Level 8

46,560 points

Mar 9, 2013 1:14 PM in response to matfish2

matfish2 wrote:

As I mentioned in my OP it seems to be called by launchd with the -l flag, which doesn't even exist on my ssh-agent installation.

No one here can comment on what exactly is in your particular ssh-agent installation. There most definitely is a "-l" flag in the OS X 10.2 implementation of ssh-agent.

For whatever reason, your version of OS X is different than ours. OS X is not Linux. You don't need to hack up the operating system and make low level changes just to make it work. If you are unable to identify and reverse the changes that you have made, then you need to erase your hard disk and reinstall the operating system.

If you at least meet us halfway and tell us what you have done, then we might be able to tell you how to undo it. Failing that, reinstall the OS.