Consider providing an affordance to override cert errors like weak crypto such as RC4

RESOLVED INACTIVE

Status

()

Firefox for Android
General
RESOLVED INACTIVE
3 years ago
19 hours ago

People

(Reporter: sworkman, Unassigned)

Tracking

44 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

In Bug 1207137 we added support to override RC4-related cert errors. We should consider doing the same in Firefox for Android.
(Reporter)

Updated

3 years ago
See Also: → bug 1207137
(Reporter)

Comment 1

3 years ago
Margaret, can we use the strings from desktop for this?
Flags: needinfo?(margaret.leibovic)

Comment 2

3 years ago
(In reply to Steve Workman [:sworkman] (please use needinfo) from comment #1)
> Margaret, can we use the strings from desktop for this?

Unfortunately we don't build Fennec with the strings in /browser. We could use the same strings, but the entities would need to be copied into the mobile netError.dtd, which would break string freeze.

If this is something we want to chase for Fx44, maybe we could get permissions to land and uplift those. But given the fact that we don't have anyone ready to do this work, maybe this is better left to Fx45 anyway.

It looks like right now both /browser and /mobile have overrides for the shared netError.dtd in /dom :/
Flags: needinfo?(margaret.leibovic)
(Reporter)

Comment 3

3 years ago
Thanks Margaret. Seems like Fx45 might be the best option. Right now, Bram (cc'ing) is experimenting with making the neterror pages responsive - hopefully that will be done for 45.

Adding Richard too.
Flags: needinfo?(rlb)
Flags: needinfo?(bram)
(Reporter)

Comment 4

3 years ago
Sigh. Meant to cc, not needinfo.
Flags: needinfo?(rlb)
Flags: needinfo?(bram)

Comment 5

3 years ago
My experiment in making error pages responsive (see bug 1217269) has to do with stylesheet rather than HTML. Would this suffice for the purpose of this project, or do we need something more?

Comment 6

3 years ago
(In reply to Bram Pitoyo [:bram] from comment #5)
> My experiment in making error pages responsive (see bug 1217269) has to do
> with stylesheet rather than HTML. Would this suffice for the purpose of this
> project, or do we need something more?

If we're not combining the HTML/JS, we would have to implement something similar to bug 1207137 for the mobile HTML/JS files. In the short-term, that would be much simpler than trying to un-fork the code, if the main goal is to add this override.

Comment 7

3 years ago
(In reply to :Margaret Leibovic from comment #6)
> If we're not combining the HTML/JS, we would have to implement something
> similar to bug 1207137 for the mobile HTML/JS files. In the short-term, that
> would be much simpler than trying to un-fork the code, if the main goal is
> to add this override.


This sounds practical. Merging the mobile and desktop page should be an end goal, but in the short term, at least we share the same stylesheet.

I have no idea how this will translate to iOS. I’m hoping that we can do the same thing here, but that may be out of the scope of this bug.

Comment 8

19 hours ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 19 hours ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.