|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Loosing digital signature of macros after storing document | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | App Dev | Reporter: | benzman1981 <webmaster> | ||||||
| Component: | api | Assignee: | joachim.lingner | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | issues@api <issues> | ||||||
| Severity: | Trivial | ||||||||
| Priority: | P3 | CC: | issues | ||||||
| Version: | 3.3.0 or older (OOo) | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||
| Developer Difficulty: | --- | ||||||||
| Attachments: |
|
||||||||
|
Description
benzman1981
2007-08-28 12:04:30 UTC
Created attachment 47821 [details]
The sample document with a signature for macros
Created attachment 47822 [details]
The java snippet to reproduce the behavior
that is exactly the concept and principal of digital signatures. When you change something the signature gets lost. You have to sign the document again after any kind of changes on the document. invalid -> closed Well then how do You sign the document afterward through the API? I would have tried this, but I could not found any snippets for this. Regards, Markus After some research and after a hint of one of our customers the concept You mentioned is correct for signing the document itself. This is why the OpenOffice.org application gives the user a hint that all document signatures will be removed if it is change. So far so good. But the concept You stated does not seem to be correct for signing macros. If I change a document that hase signed macros with the OpenOffice.org application and save it again, then all signatures for macros are still available. If I do this through the UNO API then the signatures are lost. This is inconsistent as either both, the OpenOffice.org application and the UNO API, should remove the signatures for the macros after saving a changed document, or both should not touch the signatures and leave them in the document. Regards, Markus i agree that the behaviour should be the same and assign the issue to the responsible engineer Do you have some test code available which uses the API? If yes, could you attach it to this issue? Have a look at the attachments. There is a java snippet MacroSignatureExample.java. What behavior for the signatures for macros will be choosen? Will the API be changed so that the signatures for macros will not be lost after saving through the API, or will the OpenOffice.org application be changed, so that the signatures for macros will be removed after saving? If the API will no be changed and the signatures will be lost after saving, how is it possible to set the signature again afterwards through the API? Retargeted to 3.0 Retargeting. Saving the document may not break the macro signature. *** This issue has been marked as a duplicate of 85308 *** Wrong duplicate . *** This issue has been marked as a duplicate of 85306 *** . |