path: root/xmlsecurity/inc/documentsignaturemanager.hxx
diff options
authorMiklos Vajna <>2016-03-04 10:49:12 +0100
committerMiklos Vajna <>2016-03-04 11:48:48 +0100
commite89610dad647ea5c77805ff06af1ea9870ae9f15 (patch)
tree12964e3657c079792fe218c3750e339b1c775262 /xmlsecurity/inc/documentsignaturemanager.hxx
parent38c39dc49c502683a3ccbcbfaa7e7ecee413c30f (diff)
xmlsecurity OOXML export: only cache existing signatures, not our temp. one
When adding a signature, first we export it to a temp. storage, then read it back, show the verification to the user, and then later we do or do not write the temp. storage back to the original one. This means the signature gets exported two times, and MSO only considers the final result valid. So when caching signatures (to avoid a real export based on our data model), don't cache the one we just added to the temp. storage, but do a real export second time as well. With this, MSO considers our appended signature (next to an existing one) valid, too. Change-Id: I4d615298463e037ea4e654ff5c3addcef8b0a094
Diffstat (limited to 'xmlsecurity/inc/documentsignaturemanager.hxx')
1 files changed, 1 insertions, 1 deletions
diff --git a/xmlsecurity/inc/documentsignaturemanager.hxx b/xmlsecurity/inc/documentsignaturemanager.hxx
index 6719c2613111..b5a7e1b83871 100644
--- a/xmlsecurity/inc/documentsignaturemanager.hxx
+++ b/xmlsecurity/inc/documentsignaturemanager.hxx
@@ -54,7 +54,7 @@ public:
/// Add a new signature, using xCert as a signing certificate, and rDescription as description.
bool add(const css::uno::Reference<css::security::XCertificate>& xCert, const OUString& rDescription, sal_Int32& nSecurityId);
/// Read signatures from either a temp stream or the real storage.
- void read(bool bUseTempStream);
+ void read(bool bUseTempStream, bool bCacheLastSignature = true);