summaryrefslogtreecommitdiffstats
path: root/connectivity/source/cpool/ZConnectionWrapper.cxx
diff options
context:
space:
mode:
authorMiklos Vajna <vmiklos@collabora.com>2024-10-01 11:16:04 +0200
committerMiklos Vajna <vmiklos@collabora.com>2024-10-01 12:31:48 +0200
commit298c2d5c8a6791aa6e5846b698d521079aaa445d (patch)
treef362e204cc0e9b52e10ce2674a8d0ddb244928b6 /connectivity/source/cpool/ZConnectionWrapper.cxx
parentalso set TMP in addition to TMPDIR (diff)
downloadcore-master.tar.gz
core-master.zip
cool#9992 lok doc sign: update sign status after modify the list of trusted CAs HEADmaster
Load a document, sign it, "green" icon on the status bar. Reload the document, turns into a "yellow" icon saying the CA is not trusted, when it was already trusted before. The trouble is that the document signature status is calculated on load, and the CA to be trusted is only given later, as part of the initialization of the LOK view. Fix the problem by invalidating the signature state when a new CA is trusted. The test document was produced by signing an empty document using the keys from xmlsecurity/qa/xmlsec/data/, which gives us a way to create a signature that is initially not trusted. Change-Id: I1e1dbf616ce54c4823d62104f838342de6870f52 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/174307 Tested-by: Jenkins Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
Diffstat (limited to 'connectivity/source/cpool/ZConnectionWrapper.cxx')
0 files changed, 0 insertions, 0 deletions