Hi.
On Wed, Feb 05, 2014 at 01:38:41PM -0800, Russ Allbery wrote:
> Sam Couter writes:
>
> > I use the SSH authentication and transport method, which means Amanda
> > uses SSH to connect to the clients as the backup user to run amandad. I
> > have set the authorized_keys file for the backup user
Colin Watson writes:
> It worries me a bit that this breaks amanda. I think this is the main
> thing holding me back from closing #734946. Russ, you have more
> experience of dealing with security audits that pick this up than I do;
> what would you think of flipping the backup user's shell bac
On Wed, Feb 05, 2014 at 01:38:41PM -0800, Russ Allbery wrote:
> Sam Couter writes:
> > I use the SSH authentication and transport method, which means Amanda
> > uses SSH to connect to the clients as the backup user to run amandad. I
> > have set the authorized_keys file for the backup user to forc
Russ Allbery wrote:
> I suspect that you have your debconf priority settings set to suppress
> prompting. If you change the shell and then run:
>
> dpkg-reconfigure base-passwd
>
> and say no to the question of whether you want update-passwd to change the
> shell, it will leave it alone and
Sam Couter writes:
> I use the SSH authentication and transport method, which means Amanda
> uses SSH to connect to the clients as the backup user to run amandad. I
> have set the authorized_keys file for the backup user to force the
> amandad command, but this is executed using the login shell.
Package: base-passwd
Version: 3.5.32
After upgrading base-passwd on the amanda clients, amcheck starts spitting
out messages like the following:
WARNING: fw: selfcheck request failed: tcpm_recv_token: invalid size: "This
account is currently not available.\n"
I use the SSH authentication and tr
6 matches
Mail list logo
