1157226 – Update to newer version to support yubikey neo smartcard feature

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1157226 - Update to newer version to support yubikey neo smartcard feature

Summary: Update to newer version to support yubikey neo smartcard feature

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	pcsc-lite-ccid
Sub Component:
Version:	7.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Bob Relyea
QA Contact:	Asha Akkiangady
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2014-10-26 11:07 UTC by M. Scherer
Modified:	2015-11-19 13:01 UTC (History)
CC List:	7 users (show)
Fixed In Version:	pcsc-lite-ccid-1.4.10-9.el7
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:	Hardware
Last Closed:	2015-11-19 13:01:19 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
First patch (3.14 KB, patch) 2014-10-27 06:28 UTC, M. Scherer	no flags	Details \| Diff
2nd patch (3.23 KB, patch) 2014-10-27 06:29 UTC, M. Scherer	no flags	Details \| Diff
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2015:2414	0	normal	SHIPPED_LIVE	pcsc-lite-ccid bug fix update	2015-11-19 11:23:47 UTC

Description M. Scherer 2014-10-26 11:07:33 UTC

Description of problem:
plugging my new yubikey do not seems to work fine when it come to smartcard feature ( while it work on rawhide ). ( new one with u2f support )

I didn't found a relevant commit in the svn log of the software, but the new version requires a update of pcsc-lite ( which is likely a ABI breaking one, as far as I see ).


Version-Release number of selected component (if applicable):
1.4.10-5.el7 for pcscd-lite-ccid

How reproducible:
each time

Steps to Reproduce:
1. plug the yubikey neo on usb

2. make sure that gnome-keyring is not serving as gpg-agent ( as it doesn't support pkcs11 and gpg use it by default ). If echo $GPG_AGENT_INFO show something like "/run/user/1000/keyring-9zDvUg/gpg:0:1" ( ie, with keyring ), it is using gnome-keyring, not gpg.

3. make sure that the key is in proper mode ( see with ykpers -m ), with dmesg | grep "CCID" ( should show "Yubico Yubikey NEO OTP+U2F+CCID" or without U2F for a older yubikey )

3. run gpg --card-edit

Actual results:
Error message 
$ LC_ALL=C gpg --card-edit

gpg: selecting openpgp failed: Card error
gpg: OpenPGP card not available: Card error

( beware, if it show Unsupported certificate it mean that the gpg-agent used is the gnome-keyring one, not the one of gpg )

Expected results:
Showing the card information like :

$ gpg --card-edit
Application ID ...: D2760001240102000000000000010000
Version ..........: 2.0
Manufacturer .....: test card
Serial number ....: 00000001
Name of cardholder: [not set]
Language prefs ...: [not set]
Sex ..............: unspecified
URL of public key : [not set]


Additional info:
It work fine on rawhide, and rebasing pcsc-lite-ccid make it work on rhel 7 too.

Comment 2 M. Scherer 2014-10-27 06:27:29 UTC

Ok, after digging a bit, the only needed commits are to add the description of the driver. Here is 2 patchs that should be enough ( backport from upstream svn ).

Comment 3 M. Scherer 2014-10-27 06:28:33 UTC

Created attachment 950886 [details]
First patch

Comment 4 M. Scherer 2014-10-27 06:29:05 UTC

Created attachment 950887 [details]
2nd patch

Comment 5 Bob Relyea 2014-10-29 17:54:13 UTC

I'm willing to pick this up, since it's pretty straightfoward (simply adding the USB ID for the reader), but I don't have a yubikey to test it. More importantly Asha will need one to QA it.

It may have to wait for 7.2, since we are passed devel freeze on 7.1 and this doesn't look like a blocker.

bob

Comment 11 Bob Relyea 2015-07-06 21:50:58 UTC

fixed in pcsc-lite-ccid-1.4.10-9.el7

Comment 13 Roshni 2015-09-02 16:43:50 UTC

Based on comment 7 and comment 8, putting the bug on NEED_INFO from reporter for verification.

Comment 14 M. Scherer 2015-09-03 09:06:26 UTC

I tested with a new yubikey, following my own instruction, and it work.

However, now I face this:

https://marc.info/?l=gnupg-users&m=143299373214697&w=2

so I will investigate. As far as I know, this bug can be closed since the support is here.

Comment 15 M. Scherer 2015-09-03 09:13:43 UTC

So disregard my comment on "conflicting use", I just forgot about another gpg --card-edit session running ( ie, that's a gpg UI problem, who could have said in clearer term that gpg was running :/ )

So yeah, support is working, gonna play a bit more with it in the coming weeks.

Comment 16 Roshni 2015-09-08 18:31:52 UTC

Please get back to us by end of Sept 2015 if you have any issues relating to this bug, after which the bug will be marked verified.

Comment 17 M. Scherer 2015-09-28 12:04:48 UTC

So I did test, and it work fine. So you can consider it as ok for me. I do not know the rest of the process ( ie, next state for the bug ), sorry.

Comment 18 Roshni 2015-09-28 13:31:04 UTC

Thanks for the update M. Scherer. I wil go ahead and mark the bug verified.

Based on comment 17 marking the bug verified.

Comment 19 errata-xmlrpc 2015-11-19 13:01:19 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.

https://rhn.redhat.com/errata/RHBA-2015-2414.html

Note You need to log in before you can comment on or make changes to this bug.