Document encryption

[lgsl]

Just as is the case in TM2024, and as it was discussed here, is possible to open odt files encrypted with AES256, however once is saved the encryption is downgraded to the weaker Blowfish CFB. However, if the file is saved as docx, AES256 is maintained.

I understand that Blowfish CFB is the preferred encryption for legacy formats as doc and tmd, however most, if not all, word processors that can read and write odt, uses AES256 by default.

In TM2024 it was possible to choose the type of encryption (however it disregarded the AES256 option for odt). In TM2026 this UI was simplified, and one would asume that the best/stronger supported encryption by the file format was selected, and if the file itself was previously encrypted it would honor the chosen/industry standard encryption, after all, TM is able to open it, and even honor the encryption when saved to docx.

Steps to reproduce:

1. Create an encrypted odt file using LibreOffice or any other odt-capable editor that supports or defaults to AES256. You can check the manifest.xml inside the odt to veryfy if it was encrypted as aes256 or not.
2. Open in TM, edit and save, or simply save as without editing.
3. Check the manifest.xml generated by TM where it will be stated that the encryption algorithm used is Blowfish CFB with a SHA1/1K checksum instead of the original AES256 SHA256/1K checksum.