Description of problem: Certificate verified for "email recipient certificate" unclear. What does this mean? Is it for encrypting? The other one is for signing, so I'm guessing so, but... huh? Version-Release number of selected component (if applicable): 1.0.0-37.el5 How reproducible: Always Steps to Reproduce: 1. View certs on a formatted and enrolled card. 2. Click "Your Certificates", and click the first one (may not always be first?) 3. Click 'View' Actual results: Says that it's verified for Email Recipient Certificate. Expected results: Should be more clear about what it's used for and thus verified for. Additional info: Probably a regression, but not sure.
Since we are re-using the functionality from the xulrunner engine for much of this feature, the message you are seeing is being provided by xulrunner, not esc specifically.
per smart card login team bug council, changing component to xulrunner and targeting rhel 5.5
A screenshot would be helpful, as I currently don't have a working enrolled smartcard. Jack, is this user interface "exactly" as provided by xulrunner (psm), or does ESC use a modified version of the user interface? We usually don't change any user interface strings of firefox/xulrunner in our own copy of firefox software, because of the localization issues. It's too difficult to have our own modified UI. Should this be a string provided by core xulrunner, the right place to report the issue and to work on improvements would be bugzilla.mozilla.org, core security UI. The bug report should include a proposal for better wording. But I don't see the text Certificate verified for "email recipient certificate" When I use Firefox and click on my own personal cert I get: This certificate has been verified for the following uses: - Email signer certificate - Email recipient certificate which seems very clear to me.
Should this indeed require a change in core xulrunner, then the target rhel 5.5 is not realistic.
Jack, please see my comments above. (I saw you had commented earlier and assumed you are on cc list, but just noticed you arent.)
Hm, the bug seems to be dead now. Please reopen if you have requested info.