Download it now!
Bug 88431 - PDF signatures - RFC3161 timestamps - Send data to TSA URL and embed result in signature
Summary: PDF signatures - RFC3161 timestamps - Send data to TSA URL and embed result i...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
Depends on:
Blocks: 84881
  Show dependency treegraph
Reported: 2015-01-15 01:04 UTC by Markus Wernig
Modified: 2015-03-28 13:06 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Markus Wernig 2015-01-15 01:04:08 UTC
After a TSA URL is selected, the PDF signing code must send the required data to that URL via HTTP and retrieve a signed timestamp. This requires some calculation on the content of the previously generated PDF file.

After that, the PDF shall be signed and the result from the request to the TSA URL embedded in the signature field of the PDF.

The function should use the same HTTP settings that would be used otherwise (i.e. in other parts of LibreOffice that also connect to external HTTP servers), such as proxy settings etc.
Comment 1 Markus Wernig 2015-01-15 01:07:49 UTC
This code depends on a TSA URL being available (as it would be after,, and, but the functionality itself does not depend directly on those issues. Only a valid TSA URL is required.
Comment 2 Robinson Tryon (qubit) 2015-01-15 03:43:54 UTC
Part of Bug 84881 - Add RFC 3161 timestamp when digitally signing PDF (tracker)
Status -> NEW
Severity -> enhancement
Comment 3 Markus Wernig 2015-03-28 13:06:44 UTC
This will be in 4.5 (It's in nightly since about March 1st). Thanks for the excellent work!