On Fri, 14 Apr 2017 11:46:46 -0400 Chris Hoogendyk <[email protected]> wrote:
> With the Debian/Ubuntu 3.3.6 package on Ubuntu 16.04, as I tried to > figure out what had been done, I started out by running `dpkg-query > -L amanda-client`. Since there was no amanda user or amandbackup user > installed, I began looking at user backup. But its home > directory, /var/backups, seemed weird, and its shell > was /usr/sbin/nologin. So then what? Is it assumed that I will > manually edit known_hosts and so on? And will the ssh-auth connection > work when the client user has a shell of /usr/sbin/nologin? Or should > I change that shell to something that works? And then just start > hacking through with my normal procedures, but with a special > dumptype that incorporates client-username "backup"? I run amanda packages on debian, and they seem to have the same characteristics as those for Ubuntu. I currently run all version 1:3.4.3-1. So, what I end up with is a mixture of the two models. On the new machine, I: Change the shell for the backup user to bash: sed -i~ -e 's/backup:x:34:34:backup:\/var\/backups:\/usr\/sbin\/nologin/backup:x:34:34:backup:\/var\/backups:\/bin\/bash/' /etc/passwd Let the backup user create files, like ~/.ssh and .bash_history. chown backup /var/backups Only then do I do the key setup for SSH. I do it as user 'backup' so that backup owns all the relevant files. Since I run all debian, all my clients and servers run amanda as user 'backup'. So I don't have the user name problem you have. I guess you can address that in the relevant ~/.ssh/config or in amanda's configuration. -- The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no Warrants shall issue, but upon probable cause, supported by Oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized. -- U.S. Const. Amendment IV Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
