public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} rdiff-backup: push or pull?
Date: Fri, 19 Aug 2011 10:13:23 -0700	[thread overview]
Message-ID: <CAN0CFw3uDLBB9cGdULyfMWHXjNF1Q_tf4F7yqqC+2a=sBr0umA@mail.gmail.com> (raw)
In-Reply-To: <2884642.1cRRdxvC51@eve>

>> I created the backup users and everything works as long as the backup
>> users have shells on the backup server and are listed in AllowUsers in
>> /etc/ssh/sshd_config on the backup server.  Did I do something wrong
>> or should the backup users need shells and to be listed in AllowUsers?
>
> I'm not too familiar with rsync backups. A shell might be required, but if you
> set the command run on the server-side in the "authorized_keys" it should
> prevent any other command from being run.

I'm actually talking about rdiff-backup.  I'm prompted for a password
if the backup user doesn't have a shell.  Are you able to rdiff-backup
without a shell on the backup server?

>> Should I set up any extra restrictions for them in sshd_config?
>
> I have disabled all password-logins and only allow shared-key logins.

I want to be prompted for a password with my normal user but I want
the backup users to be restricted.  I tried
'ChallengeResponseAuthentication no' within a Match block for a backup
user but ChallengeResponseAuthentication isn't allowed in a Match
block.  Are my options to restrict all users or none?

- Grant



  reply	other threads:[~2011-08-19 17: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 [this message]
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
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='CAN0CFw3uDLBB9cGdULyfMWHXjNF1Q_tf4F7yqqC+2a=sBr0umA@mail.gmail.com' \
    --to=emailgrant@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