New subject: [Bug 1227033] pcscd should not start on systems without appropriate hardware

Monday, 1 June 2015

https://bugzilla.redhat.com/show_bug.cgi?id=1227033

            Bug ID: 1227033
           Summary: pcscd should not start on systems without appropriate
                    hardware
           Product: Red Hat Update Infrastructure for Cloud Providers
           Version: 2.0
         Component: Documentation-Installation_Guide
          Severity: medium
          Assignee: hhudgeon(a)redhat.com
          Reporter: sammybreding(a)gmail.com
        QA Contact: mhideo(a)redhat.com
                CC: davidz(a)redhat.com, jhrozek(a)redhat.com,
                    ludovic.rousseau(a)gmail.com, ma(a)jgs-wg.de,
                    pbrobinson(a)gmail.com, rrelyea(a)redhat.com,
                    rstrode(a)redhat.com, triage(a)lists.fedoraproject.org,
                    tsanders(a)redhat.com, tuju(a)iki.fi, wwoods(a)redhat.com

+++ This bug was initially created as a clone of Bug #233762 +++

There's really no point in starting pcscd on systems without smartcard
hardware.
It should get started when the hardware is attached, either by HAL callouts or
a
udev rule.

--- Additional comment from Ludovic Rousseau on 2007-03-24 16:57:58 EDT ---

That would be a good idea but what would happen to an application waiting for
the first reader to be connected if pcscd is not already running?

--- Additional comment from Bob Relyea on 2007-03-26 14:00:32 EDT ---

It can be started late, but must be started before the first application that
potentially needs it. Tokens can be hot plugged, and some tokens have the
readers built into them, so there is no attached hardware until the token is
plugged in.

If smart card login is not enabled, it can be started after initial login, for
instance.

--- Additional comment from Ludovic Rousseau on 2007-03-27 02:49:47 EDT ---

It looks like Apple is doing something like that.

pcscd is started only when a reader is connected. But an application can do a
SCardEstablishContext even 
if pcscd is not started.

I/you/we should have a look at the pcsc-lite implementation by Apple to reuse
some ideas.

--- Additional comment from Bug Zapper on 2008-04-03 19:46:43 EDT ---

Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

--- Additional comment from Will Woods on 2008-04-04 18:10:42 EDT ---

Still happens in rawhide. It's been a year now. Any progress here?

I seem to recall that we stopped installing pcsc-lite by default in F8
specifically for this reason.

--- Additional comment from Ludovic Rousseau on 2008-04-05 07:32:13 EDT ---

It is a "limitation" of pcsc-lite.

If you want you can install libpcsclite (linked to the application like gdm)
and do not install pcscd. pcscd 
can be installed later when needed.

The use of HAL or udev to start pcscd is also a good idea. But that will not
work with serial readers (not 
used much nowadays I think).

--- Additional comment from Bob Relyea on 2008-04-07 11:41:20 EDT ---

Ludovic, I think that is fine, since serial readers are not plug and play to
begin with. having one extra step (setting pcscd to always start) in the
instructions seems find to me.

bob

--- Additional comment from Bug Zapper on 2008-05-13 22:41:39 EDT ---

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from Bug Zapper on 2009-06-09 18:31:00 EDT ---

This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from Peter Robinson on 2009-06-12 07:30:42 EDT ---

Updating version as i'm pretty sure this is still an issue.

--- Additional comment from Peter Robinson on 2009-08-13 12:46:57 EDT ---

Is this still an issue. I know this was fixed for bluetooth during the F-11
devel cycle. Maybe the same fix can be used here.

--- Additional comment from Bug Zapper on 2009-11-16 02:55:02 EST ---

This bug appears to have been reported against 'rawhide' during the Fedora 12
development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from Peter Robinson on 2009-11-20 05:44:07 EST ---

Any update on this. To have the same capabilities as Bluetooth has in F-12
would be great for both powersaving and loading.

--- Additional comment from Bug Zapper on 2010-11-04 08:11:44 EDT ---

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from Bug Zapper on 2010-12-05 02:16:43 EST ---

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

--- Additional comment from Juha Tuomala on 2011-02-01 02:15:17 EST ---

Still applies to f14.

--- Additional comment from Ludovic Rousseau on 2011-02-01 04:08:56 EST ---

f14 has pcsc-lite-1.6.4-2.fc14 so the auto start mechanism described in
http://ludovicrousseau.blogspot.com/2010/09/pcscd-auto-start.html should be
available.

It should be a good idea to upgrade f14 to pcsc-lite 1.6.6

--- Additional comment from Will Woods on 2011-02-03 14:52:42 EST ---

1.6.6 is already in F15, so this bug will be solved when F15 comes out either
way.

If there are major differences between pcsc-lite 1.6.4 and 1.6.6, it might make
more sense to just close this bug with a resolution of NEXTRELEASE.

--- Additional comment from Peter Robinson on 2011-06-11 09:42:51 EDT ---

Fixed in F-15

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=p959iNMtN5&a=cc_unsubscribe

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

[Bug 1227033] New: pcscd should not start on systems without appropriate hardware