Re: new reject msg from an arm64 buster install -- /usr/bin/tar executable?

On Tue, 3 Sep 2019 15:22:11 -0400
Nathan Stratton Treadway <[email protected]> wrote:

> Charles,
> Am I correct that on jhegaala, Amanda continues to work correctly if
> you have both
> =============
> runtar:gnutar_path=/bin/tar
> runtar:gnutar_path=/usr/bin/tar
> =============
> in your amanda-security.conf file (rather than only the second one,
> as I believe you have currently)?

Using amcheck:

The second one is indeed what I have now. That works.

/bin/tar only fails.

Both, as you proposed above, works. Swapping the two lines also works.

Neither line, and it fails.

> 
> And, does it continue to work correctly if you put the /bin/tar line
> after the /usr/bin/tar line?

Yes.

For hawk:

/bin/tar only works.

/usr/bin/tar only fails.

Both lines together works, regardless of order.

Neither line: works.


Based on these experiments, I suggest it will be easier for the
installer to simply leave both lines enabled. I am not greatly worried
about the security of leaving both enabled: if a bad guy can plop his
own version of tar down in either of those two locations, you have
other more immediate problems.

-- 
"When we talk of civilization, we are too apt to limit the meaning of
the word to its mere embellishments, such as arts and sciences; but
the true distinction between it and barbarism is, that the one
presents a state of society under the protection of just and
well-administered law, and the other is left to the chance government
of brute force."
- The Rev. James White, Eighteen Christian Centuries, 1889
Key fingerprint = 38DD CE9F 9725 42DD E29A  EB11 7514 6D37 A332 10CB
https://charlescurley.com