On 8/29/06, Alexander Hall <[EMAIL PROTECTED]> wrote:
(Since Greg's intention was to send this to the list, I reply to the
entire message)
Greg Thomas wrote:
> On 8/26/06, Alexander Hall <[EMAIL PROTECTED]> wrote:
>> Greg Thomas wrote:
>>
>> > [EMAIL PROTECTED] sudo test.sh
>>
>> > debug1: ident
(Since Greg's intention was to send this to the list, I reply to the
entire message)
Greg Thomas wrote:
On 8/26/06, Alexander Hall <[EMAIL PROTECTED]> wrote:
Greg Thomas wrote:
> [EMAIL PROTECTED] sudo test.sh
> debug1: identity file /root/.ssh/identity type -1
> debug1: identity file /root/
On Mon, Aug 28, 2006 at 10:06:27AM -0700, Greg Thomas wrote:
> On 8/28/06, Alexander Hall <[EMAIL PROTECTED]> wrote:
> >Try
> > $ SSH_AUTH_SOCK= ssh -v [EMAIL PROTECTED]
> >and I'll bet that the magic will go away...
>
> Now I'm a little concerned, mostly with my own memory. Which apps
> other
On 8/28/06, Alexander Hall <[EMAIL PROTECTED]> wrote:
Greg Thomas wrote:
> SSH_AUTH_SOCK=/tmp/ssh-TSTIJ24278/agent.24278
Ah! I bet this is it.
> Seems to be doing something automagical seeing [EMAIL PROTECTED] in the
> command line and grabbing debug1: Offering public key:
> /home/ethant/.ssh/
Greg Thomas wrote:
SSH_AUTH_SOCK=/tmp/ssh-TSTIJ24278/agent.24278
Ah! I bet this is it.
Seems to be doing something automagical seeing [EMAIL PROTECTED] in the
command line and grabbing debug1: Offering public key:
/home/ethant/.ssh/id_rsa.
Try
$ SSH_AUTH_SOCK= ssh -v [EMAIL PROTECTED]
an
Greg Thomas wrote:
[EMAIL PROTECTED] sudo test.sh
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Offering public key: /home/ethant/.ssh/id_rsa
I cannot reproduce this behaviour. I w
On 8/25/06, Peter H. Coffin <[EMAIL PROTECTED]> wrote:
On Fri, Aug 25, 2006 at 02:42:32PM -0700, Greg Thomas wrote:
> 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
On Fri, Aug 25, 2006 at 02:42:32PM -0700, Greg Thomas wrote:
> 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
>
On 8/25/06, Spruell, Darren-Perot <[EMAIL PROTECTED]> wrote:
> Maybe I was too verbose, from all appearances the key pair works fine
> for ethant:
>
> [EMAIL PROTECTED]:/home/ethant# ssh rice
> Last login: Fri Aug 25 00:14:42 2006 from grits
> OpenBSD 4.0-beta (GENERIC) #1083: Mon Aug 21 21:24:02
> Maybe I was too verbose, from all appearances the key pair works fine
> for ethant:
>
> [EMAIL PROTECTED]:/home/ethant# ssh rice
> Last login: Fri Aug 25 00:14:42 2006 from grits
> OpenBSD 4.0-beta (GENERIC) #1083: Mon Aug 21 21:24:02 MDT 2006
>
> Welcome to OpenBSD: The proactively secure Unix
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.
>
> Understoo
On 8/25/06, Peter H. Coffin <[EMAIL PROTECTED]> wrote:
On Fri, Aug 25, 2006 at 10:46:59AM -0700, Greg Thomas wrote:
> On 8/25/06, Alexander Hall <[EMAIL PROTECTED]> wrote:
> >Greg Thomas wrote:
> >> I've got a little backup script piping dump to ssh to my backup server
> >> rice, and I've got my
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
On Fri, Aug 25, 2006 at 10:46:59AM -0700, Greg Thomas wrote:
> On 8/25/06, Alexander Hall <[EMAIL PROTECTED]> wrote:
> >Greg Thomas wrote:
> >> I've got a little backup script piping dump to ssh to my backup server
> >> rice, and I've got my keys setup:
> >
> >> [EMAIL PROTECTED]:/home/ethant# sudo
On 8/25/06, Andreas Kahari <[EMAIL PROTECTED]> wrote:
What user is actually executing the script in the two instances?
I have two laptops backing up to host rice 4.0. I have an ethant
account on both laptops, corn 3.8, and grits, 3.9. I'm running the
same script from both laptops with just th
On 8/25/06, Alexander Hall <[EMAIL PROTECTED]> wrote:
Greg Thomas wrote:
> I've got a little backup script piping dump to ssh to my backup server
> rice, and I've got my keys setup:
> [EMAIL PROTECTED]:/home/ethant# sudo /sbin/dump -0auf - /dev/rwd0a | gzip | \
>> ssh [EMAIL PROTECTED] "cat > /g
On 8/25/06, Adam PAPAI <[EMAIL PROTECTED]> wrote:
Greg Thomas wrote:
> I've got a little backup script piping dump to ssh to my backup server
> rice, and I've got my keys setup:
>
> =
> [EMAIL PROTECTED]:/home/ethant# uname -a
> OpenBSD grits 3.9 GENERI
Greg Thomas wrote:
I've got a little backup script piping dump to ssh to my backup server
rice, and I've got my keys setup:
[EMAIL PROTECTED]:/home/ethant# sudo /sbin/dump -0auf - /dev/rwd0a | gzip | \
ssh [EMAIL PROTECTED] "cat > /grits/$(date "+%Y%m%d")_root.dump.gz"
Here you are running
Greg Thomas wrote:
I've got a little backup script piping dump to ssh to my backup server
rice, and I've got my keys setup:
=
[EMAIL PROTECTED]:/home/ethant# uname -a
OpenBSD grits 3.9 GENERIC#107 i386
[EMAIL PROTECTED]:/home/ethant# ssh rice
Last logi
19 matches
Mail list logo
