rsync all files of remote machine over SSH without root user?

I have this command to backup a remote machine. The problem is that I need root rights to read and copy all files. I have no root user enabled for security reasons and use sudo the Ubuntu way. Would I need some cool piping or something to do this?

rsync -chavzP --stats <a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="433630263103727a716d72757b6d726d71">[email protected]</a>:/ /media/backupdisk/myserverbackup/

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

I would recommend that you just use the root account in the first place. If you set it up like this:

• Configure your sshd_config on the target machine to PermitRootLogin without-password.
• Use ssh-keygen on the machine that pulls the backup to create an SSH private key (only if you don’t already have an SSH key). Do not set a passphrase. Google a tutorial if you need details for this, there should be plenty.
• Append the contents of /root/.ssh/id_rsa.pub of the backup machine to the /root/.ssh/authorized_keys of your target machine.
• Now your backup machine has root access to your target machine, without having to use password authentication.

then the resulting setup should be pretty safe.

sudo, especially combined with NOPASSWD as recommended in the comments, has no security benefits over just using the root account. For example this suggestion:

add the following to your /etc/sudoers file: rsyncuser ALL= NOPASSWD:/usr/bin/rsync

essentially gives rsyncuser root permissions anyway. You ask:

@MartinvonWittich Easy to gain a full root shell because rsync executed with sudo? Walk [m]e [through] that please.

Well, simple. With the recommended configuration, rsyncuser may now run rsync as root without even being asked for a password. rsync is a very powerful tool to manipulate files, so now rsyncuser has a very powerful tool to manipulate files with root permissions. Finding a way to exploit this took me just a few minutes (tested on Ubuntu 13.04, requires dash, bash didn’t work):

<a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="2d404c5f5944436d404c5f594443">[email protected]</a> ~ % sudo rsync --perms --chmod u+s /bin/dash /bin/rootdash
<a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="2f424e5d5b46416f424e5d5b4641">[email protected]</a> ~ % rootdash
# whoami
root
# touch /etc/evil
# tail -n1 /etc/shadow
dnsmasq:*:15942:0:99999:7:::

As you can see, I have created myself a root shell; whoami identifies my account as root, I can create files in /etc, and I can read from /etc/shadow. My exploit was to set the setuid bit on the dash binary; it causes Linux to always run that binary with the permissions of the owner, in this case root.

Having a real root is not [recommended] for good reasons. – redanimalwar 15 hours ago

No, clumsily working around the root account in situations where it is absolutely appropriate to use it is not for good reasons. This is just another form of cargo cult programming – you don’t really understand the concept behind sudo vs root, you just blindly apply the belief “root is bad, sudo is good” because you’ve read that somewhere.

On the one hand, there are situations where sudo is definitely the right tool for the job. For example, when you’re interactively working on a graphical Linux desktop, let’s say Ubuntu, then having to use sudo is fine in those rare cases where you sometimes need root access. Ubuntu intentionally has a disabled root account and forces you to use sudo by default to prevent users from just always using the root account to log in. When the user just wants to use e.g. the web browser, then logging in as root would be a dangerous thing, and therefore not having a root account by default prevents stupid people from doing this.

On the other hand, there are situations like yours, where an automated script requires root permissions to something, for example to make a backup. Now using sudo to work around the root account is not only pointless, it’s also dangerous: at first glance rsyncuser looks like an ordinary unprivileged account. But as I’ve already explained, it would be very easy for an attacker to gain full root access if he had already gained rsyncuser access. So essentially, you now have an additional root account that doesn’t look like a root account at all, which is not a good thing.

Method 2

Make use of the --rsync-path option to make the remote rsync command run with sudo privileges. Your command should then be e.g.:

rsync -chavzP --rsync-path="sudo rsync" --stats <a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="dbaea8bea99beae2e9f5eaede3f5eaf5e9">[email protected]</a>:/ .

If sudo prompts you for a password, you have to avoid that either by using a NOPASSWD privilege with the remote user account (pointless for root, may make sense in other use cases), or if you don’t want to do that:

• Make sure that the option tty_tickets is disabled for the user you
  are using, by running e.g. sudo visudo -f /etc/sudoers.d/local-rsync
  and entering:

  Defaults:your.username.for.rsync !tty_tickets

• Make sure that the option requiretty is disabled for the user you are
  using – it could be off by default. The method is the same as above.
• Seed the sudo password on the remote machine, by running e.g.
  ssh -t [email protected] sudo

Method 3

One simple way to do this is to use the graphical ssh-askpass program with sudo, this gets around the fact that sudo is not connected to the terminal and allows you to enter the password safely:

rsync -chavzPe 'ssh -X' --stats 
  --rsync-path='SUDO_ASKPASS=/usr/lib/ssh/x11-ssh-askpass sudo -A rsync' 
  <a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="5c292f392e1c6d656e726d6a64726d726e">[email protected]</a>:/ .

Of course the ssh-askpass program must be installed in the given location and you must be running an X session on the machine you are working on. There are a few variations on the ssh-askpass program which should also work (Gnome/KDE versions). Also a graphical sudo replacement program like gksu or kdesudo should also work.

Method 4

If your user has already sudo privileges which are protected with a password I would keep them as-is and only add a stanza to use rsync without a password:

%admin ALL=(ALL) ALL
%admin ALL= NOPASSWD:/usr/bin/rsync

Method 5

I ran into this problem today and solved it without the need for modifying configuration files or granting root-level permissions to user accounts. My particular set-up was that user A on machine foo had to copy all of the user directories from foo to machine bar in a backup directory that user A owned. (User A has sudo privileges on foo.)

The command I used is below. It was invoked by user A in the /home directory on foo.

sudo rsync -avu -e "ssh -i /home/A/.ssh/id_rsa -l A"  * B:/home/backup

This runs rsync as sudo so that all user directories on foo can be accessed but it tells rsync to use ssh to access machine bar using user A‘s credentials. My needs were slightly different than the question above but this allowed me to quickly get a backup of all the user directories on a particular machine I manage without mucking with the system’s configuration.

Method 6

Running rsync as daemon on the target machine allows you to do what you want.

Method 7

My solution is to use --rsync-path="sudo rsync" but it ask for password, workaround:

rsync -chavzP --stats --rsync-path="echo <SUDOPASS> | sudo -Sv && sudo rsync"  <a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="cabfb9afb88afbf3f8e4fbfcf2e4fbe4f8">[email protected]</a>:/ .

Method 8

Re-vitalizing this old thread, as still valid….
To restrict root access across server using pre-shared keys I recommend:

A) Restrict ssh-in for root in sshd

Put this into /etc/sshd/sshd_config on the client at the end (may also be in authorized keys):

Match User root
    AllowUsers <a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="b5c7dadac1f5">[email protected]</a><(dirvish) servers from which access to root is granted>
    X11Forwarding no
    AllowTcpForwarding no
    PermitTTY no

B) Force command (I did this in authorized keys, may also be in sshd_config)

command="/root/.ssh/allowed_commands.sh 2> /root/.ssh/allowed_commands_`/bin/date +%Y-%m-%d_%H-%M-%S`_stderr.log" ssh-rsa ..... (here goes the key) ......

C) Wrapper script /root/.ssh/allowed_commands.sh Rights: 700
This is based on
https://serverfault.com/questions/749474/ssh-authorized-keys-command-option-multiple-commands

#!/bin/bash
#
# You can have only one forced command in ~/.ssh/authorized_keys. Use this
# wrapper to allow several commands.

MY_PATH=`pwd`/.ssh
BASENAME=`basename $0`
STDOUT_LOG_FILE=${MY_PATH}/${BASENAME%.sh}_`/bin/date +%Y-%m-%d_%H-%M-%S`_stdout.log
find ${MY_PATH}/${BASENAME%.sh}*.log -ctime +4 | tee ${MY_PATH}/${BASENAME%.sh}_deleted_`/bin/date +%Y-%m-%d_%H-%M-%S`.log | xargs rm -f
# skip stdout? "rsync" commands have huge output and will flood FS....
# List here those which not to log stdout
COMMANDS_TO_SKIP_STDOUT=(rsync cat)

date >&2
echo I am instructed to run >&2
echo $SSH_ORIGINAL_COMMAND >&2
# skip stdout of the comand?
SKIP_STDOUT=0
for i in ${COMMANDS_TO_SKIP_STDOUT[@]}; do
 FOUND_SKIP_CMMAND=`expr "$SSH_ORIGINAL_COMMAND" : $i`
 if (( ${FOUND_SKIP_CMMAND} > 0 )) ; then 
  SKIP_STDOUT=1
 fi
done

case "$SSH_ORIGINAL_COMMAND" in
 "rsync --server --sender -vlkHogDtpre.iLsfxC --numeric-ids . <path 1>"     | 
 "rsync --server --sender -vlkHogDtpre.iLsfxC --numeric-ids . <path 2>/"    | 
 "rsync --server --sender -vlkHogDtpre.iLsfxC --numeric-ids . <path 3>/"    | 
 "cat /etc/hosts"                            | 
 "ls -alt /etc")
 # last entries for testing
 if (( ${SKIP_STDOUT} > 0 )) ; then 
      $SSH_ORIGINAL_COMMAND 
      RET_CODE=$?
  else
      $SSH_ORIGINAL_COMMAND | tee ${STDOUT_LOG_FILE}
      RET_CODE=$?
  fi
  echo "command executed" >&2
  echo "return code: " $RET_CODE >&2
  echo "output on stdout (this is the output to stderr)" >&2
  ;;
 *)
  echo "Access denied" | tee ${STDOUT_LOG_FILE}
  echo "Not in the list of allowed commands! Access denied" >&2
  echo "command not executed" >&2
  exit 1
  ;;
esac

So there is always a log (written to stderr and stored in /root/.ssh) at least from the latest run in which you can see what the command was.

If you want to set up a new command, just run it and check the stderr log.

stdout is also logged and as well passed back to the calling process, but is omitted for some commands (E.g. rsyncs would flood your filesystem)
Logs are deleted in order not to eat storage.

(All set up in my systems and working perfect)

Still a lot of degrees of freedom, but I think this explains the idea 🙂

Any Comments?

Bestest

Thilo

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0