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 GENERIC#107 i386
> [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
This means you can login with RSA key auth as root.
No, I can't:
[EMAIL PROTECTED]:/root# ssh rice
[EMAIL PROTECTED]'s password:
Permission denied, please try again.
[EMAIL PROTECTED]:/root# ^D
[EMAIL PROTECTED]:/home/ethant# ssh rice
Last login: Fri Aug 25 09:58:40 2006 from corn.2fortheroad.net
OpenBSD 4.0-beta (GENERIC) #1083: Mon Aug 21 21:24:02 MDT 2006
Welcome to OpenBSD: The proactively secure Unix-like operating system.
Please use the sendbug(1) utility to report bugs in the system.
Before reporting a bug, please try to reproduce it with the latest
version of the code. With bug reports, please try to ensure that
enough information to reproduce the problem is enclosed, and if a
known fix for it exists, include that as well.
[EMAIL PROTECTED]:/home/ethant#
Without introducing the script into the scenario it appears that my
SSH keys are setup properly for ethant.
> [EMAIL PROTECTED]:/home/ethant# cat test.sh
> #!/bin/sh
> /sbin/dump -0auf - /dev/rwd0a | gzip | \
> ssh [EMAIL PROTECTED] "cat > /grits/$(date "+%Y%m%d")_root.dump.gz"
>
> [EMAIL PROTECTED]:/home/ethant# sudo test.sh
> DUMP: Date of this level 0 dump: Fri Aug 25 00:23:42 2006
> DUMP: Date of last level 0 dump: the epoch
> DUMP: Dumping /dev/rwd0a (/) to standard output
> DUMP: mapping (Pass I) [regular files]
> DUMP: mapping (Pass II) [directories]
> DUMP: estimated 39523 tape blocks.
> DUMP: Volume 1 started at: Fri Aug 25 00:23:42 2006
> DUMP: dumping (Pass III) [directories]
> DUMP: dumping (Pass IV) [regular files]
> [EMAIL PROTECTED]'s password:
It seems you only have pubkey for the [EMAIL PROTECTED] and not for [EMAIL
PROTECTED]
:) Please verify your pubkey in your .ssh/authorized_keys for user: ethant.
As above my pubkey seems to be fine.
As per another message adding ethant to operator and removing sudo
from the scenario works fine so I'll just leave it at that.
Greg
