FEATURE: SSL security warning for loading an encrypted page should have site/cert-specific fine tuning

RESOLVED INVALID

Status

Core Graveyard
Security: UI
--
enhancement
RESOLVED INVALID
14 years ago
a year ago

People

(Reporter: Robert Rothenberg, Unassigned)

Tracking

1.0 Branch
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Build Identifier: N/A


Whenever I visit an encrypted page I get the security warning that I am entering
an encrypted page.

There is only an option to disable this warning globally. I would like to be
able to disable it for a specific site (or rather, for a specific certificate
for that site).

The message box with the warning when visiting an encrypted page should be
redesigned to have a Details button.  When pressing this button, one should be
given an SSL configuration panel (same as in Edit | Preferences | Privacy and
Security?) that includes the option to change whether it warns or does not warn
for that specific site or certificate.  

The details button could also have certificate info as well.


Reproducible: Always
Steps to Reproduce:
(Reporter)

Updated

13 years ago
Summary: FEATURE: SSL warning for loading an encrypted page should have site/cert-specific fine tuning → FEATURE: SSL security warning for loading an encrypted page should have site/cert-specific fine tuning
(Reporter)

Updated

13 years ago
Blocks: 272436
Assignee: security-bugs → kaie
Component: Security: General → Client Library
Product: Core → PSM
Version: Trunk → 1.01
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

13 years ago
Assignee: kaie → nobody

Updated

13 years ago
Component: Security: UI → Security: UI
Product: PSM → Core
QA Contact: ui

Updated

10 years ago
Version: psm1.01 → 1.0 Branch

Comment 1

2 years ago
Thanks for filing the bug.

Bug 799009 removed the existing global version of the warning prompt in question, so this bug is now "INVALID" in the sense that there's nothing to really fix.
Blocks: 799009
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID
(Assignee)

Updated

a year ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.