Bug 2122553

Summary:	NSS FIPS service indicators mark RSA-OAEP as unapproved
Product:	Red Hat Enterprise Linux 9	Reporter:	Alicja Kario <hkario>
Component:	nss	Assignee:	Bob Relyea <rrelyea>
Status:	CLOSED MIGRATED	QA Contact:	Alexander Sosedkin <asosedki>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	9.0	CC:	rrelyea
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:	Cause: Consequence: Workaround (if any): Result:	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-19 20:53:18 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:
Bug Blocks:	2100807, 2184514

Description Alicja Kario 2022-08-30 09:13:35 UTC

Description of problem:
NSS does not provide any FIPS approved mechanism for RSA-based KEM.

Version-Release number of selected component (if applicable):
nss-3.79.0-13.el9_0

How reproducible:
always

Steps to Reproduce:
1. Perform RSA-OEAP operation
2. Inspect service indicators
3.

Actual results:
the service indicator marks the operation as FIPS non-approved

Expected results:
The operation should be marked as FIPS approved.

Additional info:

Comment 4 RHEL Program Management 2023-09-19 20:48:17 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 5 RHEL Program Management 2023-09-19 20:53:18 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.