Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 879088

Summary:	pygpgme functionality not available in FIPS mode
Product:	Red Hat Enterprise Linux 7	Reporter:	Miloslav Trmač <mitr>
Component:	pygpgme	Assignee:	Miloslav Trmač <mitr>
Status:	CLOSED NOTABUG	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-22 19:45:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	879047
Bug Blocks:	839624

Description Miloslav Trmač 2012-11-22 02:57:31 UTC

pygpgme inherits the FIPS-mode algorithm/functionality restrictions of gnupg2 and its libraries.


One notable case is inability to perform symmetric encryption: The default CAST5 encryption algorithm is forbidden in FIPS mode and there is currently no fallback (#879047);  on the gnupg2 command line this can be overridden using --cipher-algo, but gpgme (and hence pygpgme) do not support specifying the algorithm through --cipher-algo.

Comment 3 Miloslav Trmač 2013-11-22 19:45:20 UTC

Bug 879047 has been fixed.

The general statement
> pygpgme inherits the FIPS-mode algorithm/functionality restrictions of gnupg2 > and its libraries.

is still true; however all major operations are now possible.  (The above-mentioned symmetric encryption uses a FIPS-approved algorithm instead of CAST5 in FIPS mode.)