336602a15d
for some reason, if xmlsecurity/qa/unit/signing/signing2.cxx is executed with CppunitTest_xmlsecurity_signing, it makes testPreserveMacroTemplateSignature10::TestBody to crash, which is weird. Split them in two Change-Id: If43085dac60f197205d70294ec22ddfc86990784 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143527 Tested-by: Jenkins Reviewed-by: Xisco Fauli <xiscofauli@libreoffice.org> |
||
---|---|---|
.. | ||
doc | ||
inc | ||
qa | ||
source | ||
test_docs | ||
uiconfig/ui | ||
util | ||
workben | ||
AllLangMoTarget_xsc.mk | ||
CppunitTest_qa_certext.mk | ||
CppunitTest_xmlsecurity_dialogs_test.mk | ||
CppunitTest_xmlsecurity_pdfsigning.mk | ||
CppunitTest_xmlsecurity_signing.mk | ||
CppunitTest_xmlsecurity_signing2.mk | ||
Executable_pdfverify.mk | ||
IwyuFilter_xmlsecurity.yaml | ||
Library_xmlsecurity.mk | ||
Library_xsec_xmlsec.mk | ||
Makefile | ||
Module_xmlsecurity.mk | ||
README.md | ||
UIConfig_xmlsec.mk |
Stuff for Document Signing
This code provides dialogs, and infrastructure wrapping libxmlsec
and
gpgme
that implements document signing.
For signing a document, a personal key pair is used, which consists of a private key and a public key, which is added to the document in addition to the digital signature of the document, when signing it.
The document signing can be done both for the source ODF/OOXML files and the exported PDF files. It is also possible to sign existing PDF files.
To test the signed PDFs, one can use the pdfverify
in this way:
./bin/run pdfverify $PWD/xmlsecurity/qa/unit/pdfsigning/data/2good.pdf
The file parameter should be an absolute path.
This is the output of pdfverify
for 2good.pdf
:
verifying signatures
found 2 signatures
signature #0: digest match? 1
signature #0: partial? 0
signature #1: digest match? 1
signature #1: partial? 0