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 1667941 - 3des tests failures due to FIPS incompatible test scenarios
Summary: 3des tests failures due to FIPS incompatible test scenarios
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: opencryptoki
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 8.1
Assignee: Than Ngo
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On: 1498625 1651238 1682530
Blocks: 1624641 1701002
TreeView+ depends on / blocked
 
Reported: 2019-01-21 13:50 UTC by Karel Srot
Modified: 2020-11-14 15:49 UTC (History)
5 users (show)

Fixed In Version: opencryptoki-3.11.0-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:04:17 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 174870 0 None None None 2019-06-12 07:29:18 UTC
Red Hat Product Errata RHBA-2019:3524 0 None None None 2019-11-05 22:04:44 UTC

Description Karel Srot 2019-01-21 13:50:49 UTC
Description of problem:

Hello,
when running the test suite for opencryptoki-3.10.0-3.el8.s390x I am getting 20 Failures for

./des3_tests  -slot 1

having

Token #1 Info:
	Label: ibmtest                         
	Manufacturer: IBM Corp.                       
	Model: IBM ICA         
	Serial Number: 123             
	Flags: 0x44D (RNG|LOGIN_REQUIRED|USER_PIN_INITIALIZED|CLOCK_ON_TOKEN|TOKEN_INITIALIZED|)
	Sessions: 0/18446744073709551614
	R/W Sessions: 18446744073709551615/18446744073709551614
	PIN Length: 4-8
	Public Memory: 0xFFFFFFFFFFFFFFFF/0xFFFFFFFFFFFFFFFF
	Private Memory: 0xFFFFFFFFFFFFFFFF/0xFFFFFFFFFFFFFFFF
	Hardware Version: 1.0
	Firmware Version: 1.0
	Time: 12:44:19

Using slot #1...

With option: no_stop: 0

Total=9, Ran=9, Passed=9, Failed=0, Skipped=0, Errors=20

Test cases need to be updated so they are using FIPS compliant keys.

See bug 1498625#c11 for details, there is already a patch for the test cases confirmed to be working.

Comment 2 IBM Bug Proxy 2019-01-21 14:40:21 UTC
------- Comment From ifranzki.com 2019-01-21 09:35 EDT-------
Hopefully RHEL 8.1 will have OCK 3.11, which then includes these patches already.

Comment 4 Than Ngo 2019-03-26 13:22:22 UTC
it's fixed in opencryptoki-3.11.0-3.el8

Comment 8 errata-xmlrpc 2019-11-05 22:04:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3524


Note You need to log in before you can comment on or make changes to this bug.