Bug 1013017

Summary: pkcsconf: C_GetSlotList returned 0 slots
Product: Red Hat Enterprise Linux 7 Reporter: Jiri Jaburek <jjaburek>
Component: opencryptokiAssignee: Dan Horák <dhorak>
Status: CLOSED DUPLICATE QA Contact: Jiri Jaburek <jjaburek>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: plautrba
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-20 13:21:02 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:

Description Jiri Jaburek 2013-09-27 15:22:43 UTC
Description of problem:

Any pkcsconf operation returns the following error:

C_GetSlotList returned 0 slots. Check that your tokens are installed correctly.

The opencryptoki-swtok package is installed, pkcsslotd is running without any apparent errors/warnings.

Copying RHEL6 binaries pkcs11_startup and pkcs_slot to this RHEL7 machine and run pkcs11_startup doesn't help, the error still appears.


Version-Release number of selected component (if applicable):
opencryptoki-swtok-3.0-4.el7.x86_64
opencryptoki-3.0-4.el7.x86_64
opencryptoki-libs-3.0-4.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. install aforementioned packages
2. start up pkcsslotd (if it's not running)
3. run ie. pkcsconf -t

Actual results:
pkcsconf -t outputs an error message

Expected results:
pkcsconf -t outputs info about tokens available (ie. soft token), like on RHEL6

Additional info:

Comment 1 Petr Lautrbach 2013-09-27 15:25:44 UTC
There's a problem with initialization of new software token. pkcs11_startup from older release can be used as temporary workaround.

Comment 4 Dan Horák 2014-01-13 10:03:41 UTC
sounds bug #1045775 outlines a solution

Comment 5 Dan Horák 2014-01-20 13:21:02 UTC

*** This bug has been marked as a duplicate of bug 1054442 ***