Bug 1032315

Summary:	attrcrypt fails to find unlocked key
Product:	Red Hat Enterprise Linux 6	Reporter:	Rich Megginson <rmeggins>
Component:	389-ds-base	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED ERRATA	QA Contact:	Sankar Ramalingam <sramling>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	jgalipea, nhosoi, rmeggins, vashirov
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.2.11.15-34.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1032316 (view as bug list)		Environment:
Last Closed:	2014-10-14 07:52:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1032316, 1061410

Description Rich Megginson 2013-11-20 00:36:57 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47596

When doing client cert based authentication for replication or chaining, and attrcrypt attempts to find the server's cert and key, it can get confused and attempt to use the wrong key.  Apparently in openldap's NSS implementation, the cert can end up on a token that has not been logged out, and the server will try to read the pin for the token/slot on stdin.

Comment 2 Sankar Ramalingam 2014-06-19 11:17:55 UTC

Request you to add steps to verify bugzilla.

Comment 3 Rich Megginson 2014-06-19 14:19:02 UTC

(In reply to Sankar Ramalingam from comment #2)
> Request you to add steps to verify bugzilla.

I found this bug running the mmrepl/accept tests.  To verify, make sure you do not see any attrcrypt error messages in the errors log for any of the suppliers/consumers during the mmrepl/accept tests.

Comment 4 Viktor Ashirov 2014-07-22 12:34:37 UTC

No attrcrypt errors were observed during mmrepl/accept tests run. Hence marking as verified.

Comment 5 errata-xmlrpc 2014-10-14 07:52:16 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.

http://rhn.redhat.com/errata/RHBA-2014-1385.html