From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} rdiff-backup: push or pull?
Date: Sat, 20 Aug 2011 10:12:35 +0200 [thread overview]
Message-ID: <2784652.DcThESz1aH@nazgul> (raw)
In-Reply-To: <CAN0CFw2tt6KvUjHNoY7g=SKNK8xLG2G-FtFUQr2pf-bOnGCNUw@mail.gmail.com>
On Fri 19 August 2011 12:58:10 Grant did opine thusly:
> >> Is the purpose of the Host block in .ssh/config to store the
> >> hostname of the backup server so it doesn't need to be used
> >> directly in the rdiff-backup command?
> >
> > It forces key-based authentication when connecting to the backup
> > server. The default is password-based, which obviously won't
> > work in a cron job.
> I don't use an .ssh/config at all and I'm not prompted for a
> password if the keys are in place. My sshd_config is pretty much
> default and my normal user is prompted for a password.
sshd can use various schemes for user authentication. The overall
process is:
user connects
user is authenticated somehow
user's shell is launched
The middle step is highly variable. sshd can do all of it itself using
only keys, or it could be happy with password authentication, it can
even use PAM and obey whatever yes/no result PAM comes back with.
sshd runs as root (therefore with access to /etc/shadow) so it could
even validate passwords itself if it wanted, bypassing login and PAM
entirely. This is of course a silly idea, but still technically
feasible.
.
.ssh/config is only useful when the user desires options different
from the global defaults in /etc/ssh/sshd_config, or wants to do extra
actions for specific destination hosts
>
> >> Why create a password for the backup user? Doesn't that open
> >> up the possibility of someone logging in as that user, when
> >> otherwise the account would only be used for backing up
> >> files?
> >
> > It might work without one; in these instructions the
> > machine-to-be-backed-up never connects to the backup server as
> > root, and so you need a way to SCP stuff to the backup server.
> > I usually use a `pwgen 16` password for these accounts and then
> > immediately forget it, so nobody will log in to them for a few
> > billion years at least.
> >
> > Does key-based authentication work with no password? I've never
> > tried.
> It does! :)
>
> - Grant
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-08-20 8:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 4:58 [gentoo-user] {OT} rdiff-backup: push or pull? Grant
2011-08-16 6:35 ` Joost Roeleveld
2011-08-16 23:50 ` Grant
2011-08-17 6:07 ` Joost Roeleveld
2011-08-17 17:18 ` Grant
2011-08-18 6:13 ` Joost Roeleveld
2011-08-19 1:01 ` Grant
2011-08-19 6:07 ` Joost Roeleveld
2011-08-19 17:13 ` Grant
2011-08-17 6:14 ` Joost Roeleveld
2011-08-17 17:35 ` Grant
2011-08-19 17:14 ` Michael Orlitzky
2011-08-19 18:00 ` Grant
2011-08-19 19:06 ` Michael Orlitzky
2011-08-19 19:58 ` Grant
2011-08-20 8:12 ` Alan McKinnon [this message]
2011-08-17 6:15 ` Joost Roeleveld
2011-08-17 17:37 ` Grant
2011-08-17 18:54 ` Alex Schuster
2011-08-17 20:47 ` Grant
2011-08-17 21:49 ` Alex Schuster
2011-08-17 22:03 ` Alan McKinnon
2011-08-18 0:35 ` Peter Humphrey
2011-08-18 6:30 ` Joost Roeleveld
2011-08-19 1:51 ` Grant
2011-08-19 6:13 ` Joost Roeleveld
2011-08-19 17:35 ` Grant
2011-08-21 19:10 ` Joost Roeleveld
2011-08-16 13:39 ` Bill Longman
2011-08-16 14:04 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2784652.DcThESz1aH@nazgul \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox