https://bugs.documentfoundation.org/show_bug.cgi?id=147452
Juraj Šarinay <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Ever confirmed|0 |1 Assignee|[email protected] |[email protected] |desktop.org | Status|UNCONFIRMED |ASSIGNED --- Comment #5 from Juraj Šarinay <[email protected]> --- Thank you for reporting the bug. I was able to reproduce it on the following systems: Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6e781525c4781e1b62dfd03f0352a82386c94019 CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6e781525c4781e1b62dfd03f0352a82386c94019 CPU threads: 2; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Raster; VCL: win > The timestamp on at least any PDF being made with this bug existing is > invalid If one uses a deterministic signature scheme such as RSA PKCS#1 v1.5, the timestamps are in fact valid. The signature computed in the second pass is equal to the discarded one. Depending on the token type, one may have to enter a PIN twice. This inconvenience alone can be considered a bug. If one uses a "randomized" signature scheme such as ECDSA, the timestamps are indeed invalid. The bug is present on both Windows and Linux. A fix shall follow shortly. -- You are receiving this mail because: You are the assignee for the bug.
