Post #372,004
2/28/13 9:57:56 PM
|
root on machine1 isnt the user anderson on github
Any opinions expressed by me are mine alone, posted from my home computer, on my own time as a free American and do not reflect the opinions of any person or company that I have had professional relations with in the past 57 years. meep
|
Post #372,006
2/28/13 10:00:22 PM
|
Doesn't matter.
GitHub ties an SSH key to a single account only.
anderson@client -> root@remote -> anderson's-ssh-key@github.com
If forwarding is working, that would work. But I can't even get that far because Ubuntu is blocking forwarding as root.
anderson@client -> nonroot@remote -> anderson's-ssh-key@github.com works fine.
Regards,
-scott
Welcome to Rivendell, Mr. Anderson.
|
Post #372,008
2/28/13 10:08:28 PM
|
but that isn't what you posted
And of course key forwarding is nowhere to be found as well:
[root@host1 ~]# ssh -T git@github.com
Permission denied (publickey).
if you are root and try to ssh to git@github.com and forcing no terminal github will see the request as user root@host1 not anderson
try
[root@host1 ~]# ssh -vv -T git@github.com
and see what it is actually doing
Any opinions expressed by me are mine alone, posted from my home computer, on my own time as a free American and do not reflect the opinions of any person or company that I have had professional relations with in the past 57 years. meep
|
Post #372,009
2/28/13 10:15:28 PM
|
Re: but that isn't what you posted
If I put the private key in root's .ssh directory, the ssh to github.com works. That's not the issue.
When using forwarding the actual user should be immaterial. The problem is that the Ubuntu server is refusing to turn on forwarding when connecting as root.
Regards,
-scott
Welcome to Rivendell, Mr. Anderson.
|
Post #372,012
2/28/13 10:32:58 PM
|
never heard of /etc/init/autoforward.conf
Service Setup (Ubuntu)
Under current Ubuntu (10.04) you can create an Upstart job to run the setup script:
$ cat /etc/init/autoforward.conf
# autoforward - automatic SSH forwarding
description "automatic SSH forwarding"
start on runlevel [2345]
stop on runlevel [!2345]
respawn
exec /usr/local/bin/setup-ssh-forwards
It should not be executable. You can start it as follows:
$ sudo initctl start autoforward
autoforward start/running, process 11590
Any opinions expressed by me are mine alone, posted from my home computer, on my own time as a free American and do not reflect the opinions of any person or company that I have had professional relations with in the past 57 years. meep
|
Post #372,015
2/28/13 11:15:54 PM
|
That's port forwarding, isn't it?
I'm doing agent forwarding.
Regards,
-scott
Welcome to Rivendell, Mr. Anderson.
|
Post #372,019
3/1/13 12:35:49 AM
|
Yes it is...
I use a different programs for that stuff... "autossh"
--
greg@gregfolkert.net
PGP key 1024D/B524687C 2003-08-05
Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C
|
Post #372,010
2/28/13 10:21:27 PM
|
Re: but that isn't what you posted
anderson$ ssh nonroot@remotehost
Welcome to Ubuntu 11.10 (GNU/Linux 3.0.0-15-server x86_64)
[...]
Last login: Thu Feb 28 22:17:29 2013 from [elided]
nonroot@host1:~$ ssh -T git@github.com
Hi [elided]! You've successfully authenticated, but GitHub does not provide shell access.
As compared to:
anderson$ ssh root@remotehost
Last login: Thu Feb 28 22:16:36 2013 from [elided]
[root@host1 ~]# ssh -T git@github.com
Permission denied (publickey).
Regards,
-scott
Welcome to Rivendell, Mr. Anderson.
|
Post #372,017
3/1/13 12:13:54 AM
|
Re: but that isn't what you posted
Instead of:
[root@host1 ~]# ssh -T git@github.com
Try:
[root@host1 ~]# ssh -vvv -T git@github.com and look at the error messages.
-Mike
@MikeVitale42
"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759 Historical Review of Pennsylvania
|
Post #372,032
3/1/13 10:17:26 AM
|
The problem happens before that point.
There's no SSH_AUTH_SOCK available.
Regards,
-scott
Welcome to Rivendell, Mr. Anderson.
|
