Red Hat Bugzilla – Bug 1032315
attrcrypt fails to find unlocked key
Last modified: 2014-10-14 03:52:16 EDT
This bug is created as a clone of upstream ticket:
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.
Request you to add steps to verify bugzilla.
(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.
No attrcrypt errors were observed during mmrepl/accept tests run. Hence marking as verified.
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.