On 8/25/06, Alexander Hall <[EMAIL PROTECTED]> wrote:
Greg Thomas wrote:
> On 8/25/06, Alexander Hall <[EMAIL PROTECTED]> wrote:
>> Greg Thomas wrote:
>> Here you are running the entire script as root (using sudo), and
>> therefore ssh is run as root, which does not have your keys.
>
> Understood but how come the exact setup works from my system corn to
> rice ( but not grits to rice)? corn is 3.8, grits is 3.9, and rice is
> 4.0. Default ssh setup on all three except for:
>
> PermitRootLogin no
One possibility could be that you have, on corn, copied the private key
into /root/.ssh/, e.g. /root/.ssh/id_rsa.
That's what I gathered from the earlier messages. But there is
nothing in any of my /root/.ssh directories except for known_hosts
left over from first login post-installation before I set
"PermitRootLogin no".
>> Possible solutions:
>> 1) Add yourself to group operator, which removes the need for ``sudo''.
>
> Yep, that works fine.
>
>> 2) Use sudo only for the dump command within the script.
>> 3) Instruct ssh to use the designated key using ``-i identity_file''
Just for fun, you could test pointing the ssh command to your
~ethant/.ssh/id_rsa and see if that "helps".
Well, I'm much closer to getting my head around this now. With "-i
~/.ssh/id_rsa" it works fine. Is there a change with the defaults of
sudo and/or ssh with 4.0? Or possibly back with 3.9 since my 3.8
install works fine and the behaviour is different for my 4.0 install
(the target is 3.9 so I guess I could test from there just to see what
the behavior is)?
Greg
