Bug 1734547

Summary:	[RFE] PDF signature support in Evince
Product:	Red Hat Enterprise Linux 9	Reporter:	Andrew Mike <amike>
Component:	evince	Assignee:	Marek Kašík <mkasik>
Status:	CLOSED MIGRATED	QA Contact:	Radek Duda <rduda>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	alanm, amarirom, brclark, carl, david.sastre, hbarcomb, jwright, mkolbas, pbrobinson, rduda, sbarcomb, tpelka, tpopela
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-15 19:14:47 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andrew Mike 2019-07-30 20:20:40 UTC

1. Proposed title of this feature request
PDF Signature support in Evince

3. What is the nature and description of the request?
Evince currently does not show any signature information if the PDF is signed. Customer wants Evince to show signature information and details, in a similar way LibreOffice Draw does. That way an Evince user could easily verify that the PDF is "valid" by inspecting the signature details.

4. Why does the customer need this? (List the business requirements here)

Customer's employees work with signed PDFs on a daily basis -- not just PDFs signed by the customer itself, but from other public organizations such as the goverment, etc.

5. How would the customer like to achieve this? (List the functional requirements here)

Customer wants Evince to show signature information and details if the PDF is signed.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

When opening a signed PDF with Evince, customer would be advsed that the PDF is signed, if the signature is valid or not, and the custoemr would be able to see information and details of the signature (issuer, CA path to certificate, etc).

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

There seem to be some upstream bugs against poppler related to this:

https://gitlab.freedesktop.org/poppler/poppler/issues/64
https://gitlab.freedesktop.org/poppler/poppler/issues/464
https://gitlab.freedesktop.org/poppler/poppler/merge_requests/124
https://gitlab.freedesktop.org/poppler/poppler/issues/800

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

"The sooner the better".

9. Is the sales team involved in this request and do they have any additional input?

Sales is not involved.

10. List any affected packages or components.

evince, popper (presumptive)

11. Would the customer be able to assist in testing this functionality if implemented?

Yes.

Comment 9 Tomas Popela 2022-06-15 11:03:38 UTC

I'm moving this bug to RHEL 9 as there's no way for us to fix this in RHEL 8 as we will need to break API/ABI to implement this and poppler's ACG level in RHEL 8 is "2" which means that the API/ABI should be stable across the RHEL 8 lifecycle. In RHEL 9 we have the ACG level 4 that allows us to break API/ABI.

Comment 10 RHEL Program Management 2023-09-15 19:13:29 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 11 RHEL Program Management 2023-09-15 19:14:47 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.