Bug 117109 - PAdES signatures are invisible
Summary: PAdES signatures are invisible
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Digital-Signature-Lines
  Show dependency treegraph
 
Reported: 2018-04-19 14:09 UTC by alex
Modified: 2024-12-14 13:36 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alex 2018-04-19 14:09:30 UTC
The PAdES signatures generated by LibreOffice are invisible; is there any way to make them visible?

Relevant standard is relevant: http://www.etsi.org/deliver/etsi_ts/102700_102799/10277806/01.01.01_60/ts_10277806v010101p.pdf
Comment 1 Samuel Mehrbrodt (allotropia) 2018-04-23 12:53:58 UTC
> The PAdES signatures generated by LibreOffice are invisible

What do you mean with invisible?
Comment 2 Miklos Vajna 2018-04-23 13:06:35 UTC
The signature in a PDF file is a widget, vcl/source/gdi/pdfwriter_impl.cxx:6172 sets no location for it, so it'll be some 0x0-sized widget on the first page. If you use Adobe Acrobat to create a pdf signature, you typically insert some bitmap as a visible widget, and the crypto signature is attached to that visible widget.

Quite possibly this is related to your signature lines feature, Samuel. :-)
Comment 3 Samuel Mehrbrodt (allotropia) 2018-04-23 13:08:56 UTC
(In reply to Miklos Vajna from comment #2)
> Quite possibly this is related to your signature lines feature, Samuel. :-)

Ah yeah sounds familiar :) Thanks for clarification!
Comment 4 QA Administrators 2019-04-24 02:49:16 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2021-04-24 04:09:37 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2023-04-25 03:23:39 UTC
Dear alex,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug