https://issues.apache.org/ooo/show_bug.cgi?id=121499
Bug ID: 121499
Issue Type: DEFECT
Summary: If Microsoft Word adds another signature to document
originally signed by OOo it causes OOo to prompt
saying file is corrupt
Classification: Code
Product: framework
Version: AOO 3.4.1
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ui
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Created attachment 80037
--> https://issues.apache.org/ooo/attachment.cgi?id=80037&action=edit
A file that exhibits this behaviour. This one was signed by LibreOffice, but
the bug is the same.
When MS Word adds a signature to a document which was originally signed by Ooo,
Ooo then reports the document as being corrupt.
Repro steps:
1) Boot Ooo
3) Under File menu, click Digital Signatures
4) Now click "Sign Document" button, agree to save the document and add a
digital signature using a SHA1 cert
5) Exit Ooo
6) Open file you just created in MS Word (signature is considered valid)
8) File -> Info -> Protect Document -> Add a Digital signature
9) Choose an RSA certificate that uses a SHA1 hash (DSA is fine too)
10) Click Sign
11) Notice signatures are considered valid by Word (are on reopen too)
12) Exit Word
13) Open document in Ooo
Expected:
For file to open file and signatures to be considered valid
Actual:
Ooo will prompt saying the file is corrupt and needs to be repaired
We think the signatures are being stored correctly by MS Word, and that this is
a Ooo bug on open.
I have also filed an identical bug for LibreOffice
(https://bugs.freedesktop.org/show_bug.cgi?id=58442)
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
