Quoting Debra S Baddorf badd...@fnal.gov:
The fix I just sent is much more elegant than I originally mentioned.
I'm actually using the provided (symbol or variable) to set the user
back to the proper client login (ie the non prived user) that you
specified
in your setup configuration
On Jun 9, 2013, at 10:23 AM, Andreas Sundstrom wrote:
Manually adding setuid(11) and seteuid (11)(the id for my
dumpuser, operator)
at the tail end of common-src/krb5-security.c fixed the whole thing
AND AMCHECK AND ALSO AMDUMP WORK PERFECTLY.
Would you like to share more
On 2013-03-30 00:07, Debra S Baddorf wrote:
Amanda Users:
I've installed amanda v3.3.3 but am having trouble getting the auth
krb5
version to work.Is anybody actually using it yet?
I am actually still using krb5 - and would like to continue to do so.
When I run the xinetd as
Amanda Users:
I've installed amanda v3.3.3 but am having trouble getting the auth krb5
version to work.Is anybody actually using it yet?
When I run the xinetd as user=root it complains that
amcheck wants to be my dumpuser, operator. But it isn't happy running
xinetd as operator
