You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a file protected with a company Sensitivity Label encrypted and am trying to open it, but get an error Unrecognized file format.
import msoffcrypto
protected = './protected.xlsx'
unprotected = './unprotected.xlsx'
with open(protected, 'rb') as f:
ms_file = OfficeFile(f)
print(ms_file)
And I get FileFormatError: Unrecognized file format
Also, when checking .is_encrypted(), the file gives the same issue.
with open(protected, 'rb') as f:
ms_file = OfficeFile(f).is_encrypted()
print(ms_file)
The file is working and if I use Unencrypted reads fine. The file is not password protected, but just uses the sensitivity label as encryption.
I expected that is_encrypted should at least say True, and not just fail completely.
Not sure if the current implementation can even open these files with a sensitivity flag, even if you have the key
The text was updated successfully, but these errors were encountered:
Thank you for reporting! This is an interesting case and I hope to investigate it.
A problem, however, is that I don't have access to the Sensitivity Label feature on my devices.
I would appreciate it if you could send me an encrypted (empty) sample document or create a pull request for a fix.
I have a file protected with a company Sensitivity Label encrypted and am trying to open it, but get an error Unrecognized file format.
And I get
FileFormatError: Unrecognized file format
Also, when checking .is_encrypted(), the file gives the same issue.
The file is working and if I use Unencrypted reads fine. The file is not password protected, but just uses the sensitivity label as encryption.
I expected that is_encrypted should at least say True, and not just fail completely.
Not sure if the current implementation can even open these files with a sensitivity flag, even if you have the key
The text was updated successfully, but these errors were encountered: