Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


I've been working on an external tool to decrypt the contents of ODF containers, but two files in the container consistently fail their checksum when decrypted with AES256, even though they actually decrypt perfectly; the other files have no issues with their checksums. I have been trying to crawl the LO code for hints (esp. package/source/manifest/ManifestWriter), but am having some difficulty understanding the finer points of the code. Could someone more familiar with it have a look at this, please?

The problematic files in the ODF container are "manifest.rdf" and "Configurations2/accelerator/current.xml". Only their checksum fails, the data actually decrypts just fine. Other files in the container have no problems. The failure happens only with AES-encryption (no issues when using the Blowfish cipher).

I have not counted out the possibility that I'm doing something tremendously stupid, but it does seem like a bug in LO to me, and it would seem to have appeared with the introduction of AES.

For what it's worth, source to my Java tool/library is at https://github.com/kuschuermann/rltodfjlib A ready-to-run binary (for Java 1.6+) is at http://ringlord.com/rltodfjlib.jar Running it with "java -jar rltodfjlib.jar -v TestAES.odt" will dump useful information to the console.

Many thanks!

--Udo.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.