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

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[Steve Workman [:sworkman] (INACTIVE)]

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

Comment 1

[Steve Workman [:sworkman] (INACTIVE)]

Margaret, can we use the strings from desktop for this?

Comment 2

[:Margaret Leibovic]

(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 :/

Comment 3

[Steve Workman [:sworkman] (INACTIVE)]

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.

Comment 4

[Steve Workman [:sworkman] (INACTIVE)]

Sigh. Meant to cc, not needinfo.

Comment 5

[Bram Pitoyo [:bram]]

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

[:Margaret Leibovic]

(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

[Bram Pitoyo [:bram]]

(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

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.