diff options
author | Miklos Vajna <vmiklos@collabora.co.uk> | 2016-11-17 10:16:31 +0100 |
---|---|---|
committer | Miklos Vajna <vmiklos@collabora.co.uk> | 2016-11-17 11:38:56 +0000 |
commit | f099e1396f40584aebf3562873046f549139d042 (patch) | |
tree | 9596fc7ccf1248741c4b811d695ae879744d1366 /sd/source/ui/view/ToolBarManager.cxx | |
parent | c6ec65395c34394171ada7bd052ecd2bc1c98cf5 (diff) |
vcl PDF NSS sign: don't embed signed timestamp to the signature blob
There are several reasons to avoid doing so:
- The mscrypto backend doesn't do that, so the previous situation was
inconsistent.
- PDF provides markup to provide a timestamp, and that's automatically
part of the signed data.
- Page 10 of "PAdES Basic" specification from
<http://www.etsi.org/deliver/etsi_ts%5C102700_102799%5C10277802%5C01.02.01_60%5Cts_10277802v010201p.pdf>
explicitly requests either not writing that data, or writing it as an
unsigned attribute (probably to underline that the value is from untrusted
source, it's the signer's computer clock).
Change-Id: I35b1a9ef4a391a24e6695353d617f27c7d96d93b
Reviewed-on: https://gerrit.libreoffice.org/30926
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Jenkins <ci@libreoffice.org>
Diffstat (limited to 'sd/source/ui/view/ToolBarManager.cxx')
0 files changed, 0 insertions, 0 deletions