Bug 396391

Summary:	kscreenlocker fails with smartcard using pam_pkcs11
Product:	[Unmaintained] kscreenlocker	Reporter:	Lew Wolfgang <wolfgang>
Component:	kcheckpass	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	major	CC:	bshah, dennis.lissov, nate, null, orion, wolfgang
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Lew Wolfgang 2018-07-11 00:55:43 UTC

kscreenlocker works with shadow passwords and krb5 authentication, but fails when entering a PIN for a smartcard.  KDM works with the PIN when logging in.  kcheckpass calls pam_pkcs11 but fails with a "kcheckpass[xxxx]: no suitable token available" error.  

This is on an openSUSE Leap 15 install, and seems to be running:

kcheckpass-5.12.5-lp150.1.1.x86_64.debug

Is this a kcheckpass issue?  Maybe PAM?  But PAM works otherwise.  The smartcard reader flashes when trying to unlock, so the basic plumbing seems to be okay.

Comment 1 Nate Graham 2022-11-03 16:07:19 UTC

kcheckpass support has been removed for a couple releases now.