Issue 76318 - Creating a new document from a template removes the signature from all Macros
Summary: Creating a new document from a template removes the signature from all Macros
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.2
Hardware: All All
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on: 85306
  Show dependency tree
Reported: 2007-04-12 16:35 UTC by chanon
Modified: 2017-05-20 10:47 UTC (History)
4 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---

Example file with macro signed (10.00 KB, application/vnd.oasis.opendocument.text)
2007-04-12 16:41 UTC, chanon
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description chanon 2007-04-12 16:35:57 UTC
Using Trusted Sources with certificates for Macro Security is difficult with

When a new document is created based on a template (.ott) file, all the
signatures are removed, including the ones related to the security of the Macro
modules (Basic). So when the newly created document (based on the template with
 signed module) is reopen by the user, he is prompted again to enable/disable
macros (while the content of the macro module itself is not modified).

How to reproduce:
Sign the macro of a new document (Tools > Macros > Digital Signature) and save
it as a template e.g

Ensure that the settings for Macro security (Tools > Options > >
Security > Macro Security  : Security Level set to Medium and trusted Source >
Trusted certificates should contain the certificate used for signing.

Start Writer, file Open and selects the template in my case
a new document UntitledX will open. And the macro signature is gone!

Although this may look compatible with the initial requirements. I think this
not the best possible behavior.
Comment 1 chanon 2007-04-12 16:41:23 UTC
Created attachment 44383 [details]
Example file with macro signed
Comment 2 michael.ruess 2007-04-13 10:02:42 UTC
Reassigned to MSC.
Comment 3 marc.neumann 2007-04-13 10:13:52 UTC
macro -> reassign to jsk
Comment 4 frank 2007-09-21 21:52:26 UTC

not a bug as it works as designed. Maybe an enhancement. Let the iTeam decide.

Comment 5 malte_timmermann 2007-10-02 14:46:08 UTC
Does NOT work as designed.

Signatures for Document and Macros are separate, and when somebody modifies the
document, the macro signature does not break and is not removed.
So when using templates with signed macros, the signatures shouldn't disappear.
Comment 6 frank.loehmann 2007-10-02 16:03:00 UTC
I have updated the spec to cover this behavior. (see chapter 6.7 Macro Security)

FL->JL: Please fix the current behavior accordingly. Thank you..
Comment 7 joachim.lingner 2007-10-02 16:27:51 UTC
Comment 8 joachim.lingner 2007-10-15 16:22:18 UTC
Retargeted to 3.0.
Comment 9 joachim.lingner 2008-02-15 09:15:20 UTC
Comment 10 Mathias_Bauer 2008-04-21 16:26:14 UTC
changed component
Comment 11 joachim.lingner 2008-05-30 15:25:51 UTC
Comment 12 joachim.lingner 2008-06-23 13:17:50 UTC
jl->mav: Please take over.
Comment 13 mikhail.voytenko 2008-11-21 11:35:06 UTC
mav->jl: Sending to you as discussed.
Comment 14 joachim.lingner 2008-12-09 15:31:30 UTC
Comment 15 joachim.lingner 2009-06-17 14:13:59 UTC
@MAV: Please take over again
Comment 16 mikhail.voytenko 2009-09-22 10:50:32 UTC
Actually this issue looks like an enhancement, that does not mean that the
current behavior is correct. The current implementation is just incomplete.

The problem is that the current implementation supports only macro signatures in
loaded documents, i.e. in documents that have persistence. When a document is
created from template, it is a new document without persistence. Allowing a new
non-stored document to have a macro signature would be an enhancement, at least
from implementation point of view.

Setting the target to 3.3 because of not enough resources.
Comment 17 mikhail.voytenko 2010-07-05 14:38:25 UTC
Setting the target to OOo 3.4 since there are no resources to implement it in
Comment 18 Martin Hollmichel 2011-03-15 21:00:00 UTC
set target to 3.x since not release relevant for 3.4 release.
Comment 19 Marcus 2017-05-20 10:47:59 UTC
Reset assigne to the default "".