[email protected] wrote:
On Sun, 5 Sep 2010, Dustin J. Mitchell wrote:
On Sun, Sep 5, 2010 at 5:52 AM, Peter Norden
<[email protected]> wrote:
I tracked down the problem to the amcrypt-ossl-asym script itself.
In the
simple test case
$ echo "foo" | amcrypt-ossl-asym | amcrypt-ossl-asym -d
the output is not simply "foo" (as expected), but "foo" with some
binary
data append. The symmetrical version amcrypt-ossl works fine, btw.
You've narrowed down the problem correctly, and I think that this is a
bug in the script. Amanda expects its data consumers to correctly
handle trailing zeroes, but if amcrypt-ossl-asym is injecting random
binary data, then that is not correct. Note, however, that trailing
zeroes will cause exactly the same gzip warning. I wish there was a
way to turn this warning off, as the alternative is to frame and
unframe the datastream such that Amanda can identify and remove such
pad bytes.
Dustin
I have been using Amanda for years and it is great
I am about to implement encryption
Has this been fixed
Richard
It's fixed in next release (3.2.2), it will works only with dump done
with 3.2.2
Jean-Louis
