Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
qemu only support the ccid-card-passthru with hardware and certificates for usb-ccid currently, but not support the ccid-card-emulated with hardware and certificates for usb-ccid device.
Version-Release number of selected component (if applicable):
host info:
# uname -r && rpm -q qemu-kvm
2.6.32-342.el6.x86_64
qemu-kvm-0.12.1.2-2.334.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.check the qemu that not support ccid-card-emulated.
# /usr/libexec/qemu-kvm -device ?
...
name "usb-ccid", bus USB, desc "CCID Rev 1.1 smartcard reader"
name "ccid-card-passthru", bus ccid-bus, desc "passthrough smartcard"
...
2.fail to boot with ccid-card-emulated with hardware and certificates for usb-ccid device.
- using ccid-card-emulated with hardware
<qemu-kvm-command-line>...-usb -device usb-ccid -device ccid-card-emualated...
- using ccid-card-emulated with certificates
<qemu-kvm-command-line>...-usb -device usb-ccid -device
ccid-card-emulated,backend=certificates,cert1=cert1,cert2=cert2,cert3=cert3...
Actual results:
Expected results:
Qemu should also support the ccid-card-emulated with hardware and certificates for usb-ccid device, not only ccid-card-passthru.
Additional info:
Hi Gerd,
I donot check the rhel7 whether support the ccid-card-emulated with hardware and certificates for usb-ccid device. Should I need to clone this bug for rhel7 for tracing this issue to fix correctly ?
Best Regards.
sluo
I think it has been left out intentionally because it is unsupported. Alon?
Why do you want to have it in? Are there Customer requests?
[ yes, rhel-6 and rhel-7 should be identical here, so if we decide to enable
it on rhel-6 we should do the same on rhel-7 ]
Yep, we don't want to support it, so we left it out. About why, I guess mainly less code = less qa, less bugs, etc. . I'm not aware of any customer requests.
Use case for ccid is single-sign-on, which needs ccid-card-passthru so smartcard can be shared between host and guest.
So I'd say ccid-card-emulated should stay disabled on RHEL-7 too (unless there is customer demand).
So, just close/wountfix? Or do we have a tracker bug for device whitelist/blacklist?
There is a small problem; --disable-smartcard-nss also disables libcacard/vscclient and RHEL7 needs that.
So unless we add a separate toggle for ccid-card-emulated, we need to carry the device.
Once that is added upstream, please reassign this bug to mrezanin. If it's okay to keep ccid-card-emulated, close as WONTFIX.
Hmm. The actual smartcard emulation is in libcacard anyway, ccid-card-emulated is "only" the glue between libcacard and usb-ccid. So it might be not that bad after all to keep ccid-card-emulated, and it may be handy to have it for QE testing smardcard software in a virtual machine ...
Comments?
I think it is more of a question for QE so that they can allocate their resources. Is there an actual usecase for ccid-card-emulated apart from testing? Would we require separate testing for passthru and emulated? Is it possible to do the bulk of the tests on emulated and little more than smoke-testing passthru?
I think the most interesting use case for ccid-card-emulated is to test the guest code without a physical card reader, which allows easy autotest integration for example.
Any, yes, I think we can reduce the passthru testing to guest-does-see-the-hardware level smoke testing (plus some hotplug tests) then.
Gerd, we already have support for hardware less tests, using file defined certificates:
ccid-card-passthru + remote-viewer --spice-smartcard-certificates cert1,cert2,cert3
There might be use cases for the emulated case - having certificates on the host and not the client.