Hi Marc, On Wed, Sep 27, 2006 at 02:50:13PM +0200, Marc Lehmann wrote: > aespipe pads data to the cipher blocksize on encryption. as aespipe has no > container format there is no way this cna be avoided, but many programs > barf on the extra data appended (and give ghastly error messages), so this > should be mentioned in the manpage.
Thanks for your bug report. I think this is in fact already mentioned in the man page: | If input size is not | multiple of 16 or 512 bytes, input data is padded with null bytes so | that both input and output sizes are multiples of 16 or 512 bytes. If you can think of a wording that makes it more clear (which I cannot right now), I'd be happy to apply a patch and forward it to aespipe upstream. cheers, Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
