Open
Bug 745133
Opened 13 years ago
Updated 12 years ago
Define SeaMonkey's behaviour for SSL errors
Categories
(SeaMonkey :: Security, defect)
Tracking
(Not tracked)
REOPENED
People
(Reporter: KaiE, Assigned: KaiE)
References
Details
Attachments
(1 file, 2 obsolete files)
(deleted),
patch
|
Details | Diff | Splinter Review |
As of today, if a fatal connection error occurrs on a SSL/TLS socket, no feedback will be given to the user. This is different from we had in the past.
In my opinion this behaviour is undesirable, as it gives the user the impression of a nonworking product.
I'm trying to re-implement the fallback notification prompt, which would be shown if the application hasn't implemented specific error handling.
Unfortunately I'm facing heavy resistance against my proposal in bug 682329. Even if I succeeded, each application would have to opt in to getting the fallback notification prompts.
If you believe that having the fallback prompt implemented in the core, which you could simply activate in your product using a couple of line of code, would be beneficial for you, then I'd suggest to support me in my attempt to get that added in bug 682329.
I will attach a patch that you can use for testing.
Assignee | ||
Comment 1•13 years ago
|
||
Matches patch v8 from bug 682329
Comment 2•12 years ago
|
||
Comment on attachment 614723 [details] [diff] [review]
Patch v8
Kaie: is this patch still valid? Are you going to ask for a review?
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•12 years ago
|
Status: RESOLVED → REOPENED
Depends on: 785426
Resolution: INCOMPLETE → ---
Summary: Define SeaMonkey's default fallback behaviour for SSL error prompts → Define SeaMonkey's behaviour for SSL errors
Assignee | ||
Comment 3•12 years ago
|
||
Assignee: nobody → kaie
Attachment #614723 -
Attachment is obsolete: true
Assignee | ||
Comment 4•12 years ago
|
||
Attachment #655192 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•