Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This bug is migrated from raidzilla.sfbay.redhat.com Raidzilla Bug Id = 57788 ############################################# ----Additional comments from srs@redhat.com on 2005-09-16 10:58 ---- From Bill Burns (AOL) **** I'd like to be able to speficy "-mechanisms friendly" when adding the CoolKey module to Mac FireFox profiles. Doing this allows people to view the certs on the token before entering the PIN. Right now, the PIN prompt appears more frequently than necessary. **** ----Additional comments from ckannan@redhat.com on 2006-08-12 16:38 ---- per bug council on 08/11/2006, re-assign to rrelyea ----Additional comments from ckannan@redhat.com on 2006-09-23 16:58 ---- per bug council on 09/22 , we believe the current is capable of viewing certs without password. if not we can re-open this bug. resolving for now. ----Additional comments from ckannan@redhat.com on 2006-11-01 18:00 ---- I still need to enter password to view the certs with firefox. re-opening
pk11install has a way of marking the equivalent of 'friendly' already. The problem is on linux (and mac), with the current coolkey, there is no way to mark the token friendly because the slot does not exist at init time, it only exists once the app has started. (It's not -mechanisms friendly, see http://developer.mozilla.org/en/docs/PKCS11_Module_Specs ) NSS needs to pick up the configuration for slots that are initialized after a token has been loaded.
Upstream bug create: https://bugzilla.mozilla.org/show_bug.cgi?id=432329
*** Bug 224903 has been marked as a duplicate of this bug. ***
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 inclusion.
This will need to be picked up from upstream when the fix is in and we rebase. It looks like a 6.1 to me. Assigning to Bob to the devel_ack.
reassigning back to elio. Obviously if it's not fixed upstream, we shouldn't try to make it into 6.0. bob
Bob, I recommend a devel_ack- as there is no from upstream fix yet.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.