Bug 1387812

Summary:	Softoken still does not handle login state correctly for user db slots in FIPS mode
Product:	Red Hat Enterprise Linux 6	Reporter:	Bob Relyea <rrelyea>
Component:	nss-softokn	Assignee:	Bob Relyea <rrelyea>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.8	CC:	hkario, kengert, mreynolds, nhosoi, nkinder, rrelyea
Target Milestone:	rc
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:	2017-11-16 13:16:53 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:	1352109, 1425841, 1425952

Description Bob Relyea 2016-10-22 00:43:38 UTC

softoken has a built in FIPS login state as well as the login state of individual tokens. For tokens that don't have passwords, softoken needs to simulate those passwords. If softoken is logged in, but the underlying token doesn't know about being logged in, softoken pretends that the token is logged in to the user. This is correct behavior for tokens that don't have login state, but tokens that do have login state, this prevents the underlying token from ever getting logged in.

This creates the problem in slapd described in bug 1352109.

Bug 1387811 works around the problem for slapd, but other uses my still see the error.

Comment 4 mreynolds 2017-11-08 17:02:47 UTC

It's possible this is also an issue we are seeing in 389-ds-base with replication using SSL client authentication in FIPS mode:

https://bugzilla.redhat.com/show_bug.cgi?id=1464463

Originally we had issues with replication over SSL in FIPS mode, which was resolved, but when we use SSL client authentication it breaks again in FIPS mode.

Comment 5 Bob Relyea 2017-11-09 17:54:09 UTC

The patch for the issue described in this bug is in https://bugzilla.redhat.com/show_bug.cgi?id=1390154. This is one of two patches in softoken that need to be pushed upstream.

I don't think it's the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1464463, since the code in bug 1464463 is running with this patch.

Comment 6 Bob Relyea 2017-11-15 17:11:32 UTC

This bug is only needed if we rebase softoken. The current RHEL-6 has a different login code than RHEL7 and upstream, which support FIPS level 1 semantics.