office-gobmx/xmlsecurity
Miklos Vajna 0de900cec7 cool#9992 lok doc sign, hash extract: time for getCommandValues('Signature')
The final goal of this API is to give time & hash information about the
PDF signature, so once a 3rd-party produces the PKCS#7 signature, that
can be added to the document and the actual PDF sign can be re-run with
the same parameters.

This commit continues the replacement of XCertificate with
svl::crypto::SigningContext up to the point that the timestamp used in
svl/ can be exposed on the LOK API.

This is done by updating DocumentSignatureManager::add(),
PDFSignatureHelper::SetX509Certificate(),
vcl::filter::PDFDocument::Sign() and finally the svl::crypto::Signing
ctor to work with the signing context instead of an XCertificate
directly.

Time reporting works now, so add a test for that. The digest part still
needs doing.

Change-Id: I83f1274cd420b67194b7caf12b1027e623d4f7fe
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/176404
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
Tested-by: Jenkins
2024-11-11 21:54:23 +01:00
..
doc
inc cool#9992 lok doc sign, hash extract: time for getCommandValues('Signature') 2024-11-11 21:54:23 +01:00
qa cool#9992 lok doc sign, hash extract: time for getCommandValues('Signature') 2024-11-11 21:54:23 +01:00
source cool#9992 lok doc sign, hash extract: time for getCommandValues('Signature') 2024-11-11 21:54:23 +01:00
test_docs
uiconfig/ui [API CHANGE] XDocumentDigitalSignatures: remove deprecated / unused functions 2024-09-13 10:27:14 +02:00
util
workben cool#9992 lok doc sign, hash extract: time for getCommandValues('Signature') 2024-11-11 21:54:23 +01:00
AllLangMoTarget_xsc.mk
CppunitTest_qa_certext.mk
CppunitTest_xmlsecurity_dialogs_test.mk
CppunitTest_xmlsecurity_pdfsigning.mk cool#9992 lok doc sign, hash extract: time for getCommandValues('Signature') 2024-11-11 21:54:23 +01:00
CppunitTest_xmlsecurity_signing.mk cool#9992 lok doc sign, hash extract: initial getCommandValues('Signature') 2024-11-08 21:40:22 +01:00
CppunitTest_xmlsecurity_signing2.mk
CppunitTest_xmlsecurity_xmlsec.mk cool#9992 lok doc sign: fix import of the private key 2024-09-25 13:14:42 +02:00
Executable_pdfverify.mk cool#9992 lok doc sign, hash extract: time for getCommandValues('Signature') 2024-11-11 21:54:23 +01:00
IwyuFilter_xmlsecurity.yaml
Library_xmlsecurity.mk
Library_xsec_xmlsec.mk
Makefile
Module_xmlsecurity.mk cool#9992 lok doc sign: fix import of the private key 2024-09-25 13:14:42 +02:00
README.md
UIConfig_xmlsec.mk
UITest_xmlsecurity_gpg.mk pyuno,unotest,xmlsecurity: copy GPG test files for UITtest 2024-08-01 11:18:30 +02:00

Document Signing

Introduction

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.

Module Contents

  • doc: OpenDocument workflow legacy information with some illustrations to have an idea of the workflow, for starters check doc/OpenDocumentSignatures-Workflow.odt.
  • inc: Headers to a subset of source files inside the module, parts like source/framework have headers inside the folder.
  • qa: Unit tests for signing and shell scripts for certificates creation for testing.
  • test_docs: Documents & certificates used for testing.
  • source: More on that below.
  • uiconfig: User interface configuration for different dialogs, it is recommended to navigate from relevant source file to the .ui file linked in the class which will be under uiconfig/ui.
  • util: UNO passive registration config for GPG/ NSS.

Source Primary Contents

  • component: Main implementation of DocumentDigitalSignatures where the interaction with security environment and certificates occur.
  • dialogs: Certificate & Signatures management dialogs.
    • certificatechooser: Dialog that allows you to find and choose certificates or signatures for encryption.
    • certificateviewer: More detailed information about each certificate.
    • digitalsignaturesdialog: Main window for signatures of the documents and the start point of signing document.
  • framework: Various elements for verifying signatures and running security engine.
  • gpg: The implementation of encrypting with GPG and security environment initialization.
  • helper: Some helper classes that include signatures manager and the helpers for PDF signing, UriBinding, and XML signatures. It also include helper tools for XSecurityEnvironment.
  • xmlsec: XML, NSS, MSCrypt encryption/ signing tools, more on the low-level side of actual implementation of algorithms.

PDF Testing

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

References