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.
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".
Thanks for the tips.
I'm glad to help. I've built a little experience fiddling with
unencrypted private/public keys. One pair for backup, another for a
smtp-through-ssh-tunnel. Apart from adding a small initial delay
(noticable when on modem, albeit not used frequently enough to be
annoying), the smtp tunnel works great from any network.
/Alexander
