Github messages for voidlinux
 help / color / mirror / Atom feed
From: DottoDev <DottoDev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Firefox ignores system DNS setting
Date: Mon, 15 Nov 2021 19:38:16 +0100	[thread overview]
Message-ID: <20211115183816.coHr2PWOJi7jnBuA9Fciz02gUMwIdeWVdilrwTMoFlo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34097@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

New comment by DottoDev on void-packages repository

https://github.com/void-linux/void-packages/issues/34097#issuecomment-969203392

Comment:
> Users can configure firefox on about:preferences how they like. I don't think completely disabling DoH is a good idea, they are not forcing the usage of Cloudflare, they default to it and there is a choice in the settings between Cloudflare, NextDNS, bring your own DoH or not using DoH.

It has no negative impact turned off because it still defaults to cloudflare but it has a negative impact on the user if he changes the system dns server without checking the dns firefox uses. Also the ignorance of system-level dns settings of firefox is not something many users know about. And isn't DoH still on, as long as the box "Enable DNS over HTTPS" in the settings is checked. This flag should just allow the user to disable DoH by just unchecking the box "Enable DNS over HTTPS"

  parent reply	other threads:[~2021-11-15 18:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 17:25 [ISSUE] " DottoDev
2021-11-15 18:24 ` Duncaen
2021-11-15 18:24 ` Duncaen
2021-11-15 18:38 ` DottoDev [this message]
2021-11-15 18:45 ` Duncaen
2021-11-15 19:09 ` DottoDev
2021-11-15 19:18 ` Duncaen
2021-11-15 19:18 ` Duncaen
2021-11-15 21:53 ` DottoDev
2021-11-15 22:12 ` Duncaen
2022-06-13  2:16 ` github-actions
2022-06-28  2:15 ` [ISSUE] [CLOSED] " github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211115183816.coHr2PWOJi7jnBuA9Fciz02gUMwIdeWVdilrwTMoFlo@z \
    --to=dottodev@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).