Red Hat Bugzilla – Bug 201344
GDM shouldn't enable entry field if the Smart Card is required.
Last modified: 2007-11-30 17:07:32 EST
Description of problem:
GDM shouldn't allow any input if require smartcard is set.
Version-Release number of selected component (if applicable):
Set smart card login require to true
Try run gdm.
Try to enter a user name
You can enter a name.
No input should be accepted.
*** Bug 202140 has been marked as a duplicate of this bug. ***
shoudl be fixed in
Testing candidate 20061006.2 I was about to re-open the bug due to one boundary
case not being taken care off. Then I checked my gm version.
$ rpm -qa | grep gdm
So not -15 perhaps my boundary case is taken care of in that version. So I am
going to hold off re-opening until I re-test with -15
Steps to Reproduce:
1. Configure smart card login to require smart cards
2. At the gdm login prompt after
2.a A Reboot or
2.b A logout from the previous session by removing the smart card
The UI presented is
A text box with ... in it. Above the text box is Username. Below the text box is
Please insert your smart card.
You cannot type in the box. Good
However, Boundary case
3. Logout from the previous session with the card inserted
4. When the UI is presented to enter the pin for the named smart card, remove
the smart card
5. New UI is presented ....
A text box with nothing in it. Above the text box is, nothing, no text label
Below the text box is Please insert your smart card.
You can type in the text box - not good.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
per bug council on 11/17,
this is a rhel5 blocker.
not able to reproduce comment #0
not able to reproduce comment #3
not able to reproduce comment #7
I haven't been able to reproduce either. Given that it's not readily
reproducible, this isn't really as severe as I thought it was. I don't think
this should really be a blocker at this point.
(if it were readily reproducible, then customers would be much more likely to
hit it and it would be a much more severe problem).