Closed Bug 1613635 Opened 5 years ago Closed 5 years ago

Unchecking the “Enable DNS over HTTPS” option from “Network Settings” or setting `doh-rollout.enabled` to false does not disable the DNS feature

Categories

(Shield :: Shield Study, defect)

Desktop
All
defect
Not set
blocker

Tracking

(firefox73+ wontfix, firefox74+ wontfix)

RESOLVED INVALID
Tracking Status
firefox73 + wontfix
firefox74 + wontfix

People

(Reporter: romartin, Unassigned)

References

Details

Attachments

(1 file)

Attached image 2020-02-06_14h13_27.gif

[Affected versions]:

  • Firefox Nightly 74.0a1 - Build ID: 20200205215017
  • Firefox Beta 73.0b12 - Build ID: 20200203203546

[Affected Platforms]:

  • Windows 10 x64
  • Mac 10.15.1
  • Ubuntu 18.04 x64

[Prerequisites]:

  • Have a new Firefox profile.
  • Have the following prefs in the “about:config”
    • security.content.signature.root_hash set to DB:74:CE:58:E4:F9:D0:9E:E0:42:36:BE:6C:C5:C4:F6:6A:E7:74:7D:C0:21:42:7A:03:BC:2F:57:0C:8B:9B:90;
    • app.normandy.api_url set to https://stage.normandy.nonprod.cloudops.mozgcp.net/api/v1;
    • app.normandy.dev_modeset to true;
    • app.normandy.logging.level set to 0;
    • services.settings.server set to https://settings.stage.mozaws.net/v1;
    • ppop-doh-roll set to true;

[Steps to reproduce]:

  1. Open the browser with the profile from prerequisites.
  2. Navigate to “about:preferences” and click the “Settings…” button located at the bottom of the page underneath the “Network Settings” section.
  3. Uncheck “Enable DNS over HTTPS”.
  4. Restart the browser and navigate to about:config.
  5. Search for the doh-rollout pref and observe the page.

[Expected result]:

  • Only the doh-rollout.enabled pref is displayed and it is set to false.

[Actual result]:

  • The value of the doh-rollout.enabled pref is true and all the other prefs set by enabling the DNS over HTTPS feature remain the same.

[Notes]:

  • The issue is also reproducible if you manually change the doh-rollout.enabled pref to false and check if the value will be changed if you check the “Enable DNS over HTTPS”.
  • Because of this scenario we are unable to verify if the user would be able to re-enable the DNS over HTTPS feature.
  • We have used the following Normandy recipe (you need access to the Delivery Console in order to view it): https://delivery-console.stage.mozaws.net/recipe/927/

After discussing with the engineering team, we reached the conclusion that this behaviour is expected. Closing this as INVALID.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: