Open Bug 1018260 Opened 11 years ago Updated 2 years ago

Improve client certificate handling (login/logout, pin caching)

Categories

(Firefox :: Security, enhancement)

x86_64
Linux
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: loic.etienne, Unassigned)

References

Details

Client certificates: Log in/out, Pin prompting/caching * The client certificate currently in use should be displayed. The user should be able to log out (delete the ssl session and the pin if any). This is already possible with 'clear the recent history', but this should be also possible on a per site basis. All active ssl logins should be displayed as well (for sites the user have left). * Pin caching should be optional (configurable, asked at first prompt with a "do not ask again" check-box). For security reasons, the default should be 'disabled'. * A pin protecting the private key should not be prompted in advance. If a pkcs#11 security device does not allow to read available certificates without pin, the security device should be displayed with an 'open' button triggering a pin prompt. No prompt 'just in case', it is annoying and less secure. * The user should be informed whether a client certificate is optional or required. When a client certificate is required, clicking 'cancel' should display a corresponding error page "Client certificate required. Retry button.". When a client certificate is optional, clicking 'cancel' should continue without client certificate. Furthermore, when a client certificate is optional, the user should be able to log in and out at will. * The 'cancel' choice of the user should be respected, instead of re-prompting the pin a couple of times. Possible places: Padlock left to the url, Page Info, maybe even a new tab "Connections".
See Also: → 1074830
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.