Hi,

currently I am trying to replace our self-made backup hacks with an Amanda solution. We are using vtapes only, no physical tape drives involved.

The backups should be asymetrically encrypted (with amcrypt-ossl-asym) and compressed on the client. This works fine so far. But when I try to restore files using amrecover, it warns: "gzip returning exit status 2". The restore itself seems to work, but those warnings should not appear in a productional environment, imho.

Further investigations in the logs showed that gzip complains about the data it gets from amcrypt-ossl-asym: "gzip: stdin: decompression OK, trailing garbage ignored".

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.

I am using Amanda release 3.1.2 and OpenSSL 0.9.8 with the aes-256-cbc cipher in amcrypt-ossl-asym.

Has anybody experienced or even solved similar problems? Any workarounds? Or am I just overlooking something obvious?

Thank you in advance,

Peter

Reply via email to