As described, I already:
1) put FowardAgent yes in the config file.
2) tried -A all on its own.
That's the problem: I've done all of that and it still doesn't work; that's the point of my question, and that's why I'm asking for help.
Er, what?
As described, I already:
1) put FowardAgent yes in the config file. 2) tried -A all on its own. That's the problem: I've done all of that and it still doesn't work; that's the point of my question, and that's why I'm asking for help. Regards,
-scott Welcome to Rivendell, Mr. Anderson. |
|
Try here.
http://bridge.grumpy...hd-ssh-agent.html
http://www.dribin.or...sh_agent_leopard/ If that again addresses things that are already working, no need to reply. I'll quit. Good luck. Cheers, Scott. |
|
Thanks anyways. :-)
Regards,
-scott Welcome to Rivendell, Mr. Anderson. |
|
Ok.
First and foremost. Lay the ground work:
1. Your public part of your SSH key pair *MUST* be ~/.ssh/authorized_keys on all destination hosts. That file *MUST* have a perms of 0600 (-rw-------) and be owned by the user. 2. ALL Destination hosts must *NOT* disallow Forwarded Authentication. (this being a key point here, stupid as it may be, it is a choice over zealous admins use sometimes) ("PubkeyAuthentication yes" is usually default and only works with version 2 anyway) 3. You have your local workstation's ssh-agent running and loaded with your private part of your SSH key pair. 4. You must either by config (~/.ssh/config or /etc/ssh/config) have "ForwardAgent yes" on all hosts or use "ssh -A" on every attempt to want to forward from there. If you do not use "ssh -A" (or have config) on the "next" host, you will only be allowed to forward from that last host and no successive host. example of #4: I ssh into relay host without ForwardAgent yes or with without "-A" I can not login via key-authentication. If I ssh into relay host "ssh -A relayhost" my authentication will be forwarded one additional hop to the next host or "ssh nexthost" will auto present the key-auth. If I have "ForwardAgent yes" or use "ssh -A nexthost" I can then chain another "ssh thirdhost" and be authenticated via key-auth and so on and so on. *ALL* of these following machines have my public part of my key pair which is snipped to make it screen width friendly, otherwise it'd be over 600 characters wide: ssh-dss AAAAB3NzaC1kc3MAAACBAKLDN [SNIP] +atgu8agE= greg@gregfolkert.net That entry is in *EVERY* ~/.ssh/authorized_keys with a "0600" permissions (-rw-------) on that file. Here is a "cleansed" screen scrape output. to help make it clear and show what happens if you don't use the appropriate ForwardAgent flags of config. Most of these times are "Mountain Time". greg@maxime:~ [0] $ ssh-add -l --
greg@gregfolkert.net PGP key 1024D/B524687C 2003-08-05 Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C |
|
If that doesn't help...
Yet another reason I dislike OSX.
--
greg@gregfolkert.net PGP key 1024D/B524687C 2003-08-05 Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C |
|
Yes, all of those things are configured as described.
And I discovered that it works fine through non-root accounts. I can't forward through root on the remote machine.
Doesn't work: anderson $ ssh -A root@remotehost
Does work: anderson $ ssh -A nonroot@remotehost
So for some reason root is being blocked from forwarding, which makes no sense to me since forwarding only exposes the original client machine, not the remote. So it's not OS X... it's Ubuntu. ;-) Thanks anyways. Now I have to figure out how to convince Ansible to configure things via sudo instead (which it will do, but only for an entire playbook at a time, not just a single task). Regards,
-scott Welcome to Rivendell, Mr. Anderson. |
|
Now... ahh ha.
More than likely they are being anal retentive about Root.
Root is a crappy thing to have to use to do automated things. It happens, but many won't/don't know how to make it available. Probably comes down to a setup using some kind of PAM thing or perhaps "root" has a compiled in option for ssh/sshd to not allow things. There are weird options usable to restrict Root in custom compiled sources, all without config options evident. You should see entries in the /var/log/auth.log for me... Mar 1 00:32:57 omg sshd[30118]: Accepted publickey for root from XX.XX.XX.XX port 34837 ssh2 Mar 1 00:32:57 omg sshd[30118]: pam_unix(sshd:session): session opened for user root by (uid=0) I'd be looking as the PAM session setup, I'm betting its there. --
greg@gregfolkert.net PGP key 1024D/B524687C 2003-08-05 Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C |
|
Didn't find anything, but good idea. Thanks.
Regards,
-scott Welcome to Rivendell, Mr. Anderson. |