Red Hat Bugzilla – Bug 476006
Corrupted cache file should not cause coolkey to seg fault.
Last modified: 2009-11-18 17:37:17 EST
Description of problem:
Corrupted cache file should not cause coolkey to seg fault. Unclear how the cache file got corrupted in the first place, but it shouldn't cause a seg fault.
Version-Release number of selected component (if applicable):
Always, with a corrupted cache file
Steps to Reproduce:
1. Lock screen. Use PIN to unlock.
2. run "certutil -L -h all -d /etc/pki/nssdb" x3
First try will not prompt for PIN.
Second try will seg fault.
Third try will prompt for PIN and succeed.
Should always prompt and succeed if correct PIN is used.
Not a regression, since coolkey was not changed in this update.
per bug council, shifting to rhel6
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
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.