On 2/25/20, Paul Bergsagel <[email protected]> wrote:
> Hi,
>
> Does SeaMonkey support DoH and if it does how can it be enabled?

apparently not

> Also does anyone know the pros and cons of using DoH?

Pro - hide your dns traffic from your ISP, sidestep ISP/Country blocks
for "bad" hostnames

Con - google. cloudflare, whatever sees all your name resolution
requests, no ability to monitor or block name resolution requests on
your own (eg. family safe or gambling filters)

If you think you might want DOH then you should take a look at TOR
  https://www.torproject.org/
better privacy, but riskier since anyone can put up an exit node and
do whatever (at the very least, do not enable javascript from
unencrypted pages)


I did a quick look for DOH links - you might want to take a quick look at

http://www.circleid.com/posts/20191212_whats_behind_the_secure_dns_controversy_doh/
  From Mozilla's perspective, the move to DoH is quite simple: it
provides users with greater privacy and security.
  ...
Erwin points out that in the US, ISPs specifically — and successfully
— lobbied to be released from new rules that would have prevented them
from selling or sharing user data and gives several examples where
user data has already been monetized.


https://www.freezenet.ca/mozilla-accuses-isps-of-lying-to-congress-about-doh-encryption/
  Then, in late October, news broke that suggests that big US ISPs are
also behind the push to put an end to DoH encryption. A leaked Comcast
slideshow destined for congress urges lawmakers to put an end to such
encryption. Many point out that the motivation to stop this is likely
revolving around ISPs pushing tracking and advertising onto their
customers. DoH encryption stands to thwart such an effort, so it may
be at least one motivating factor why ISPs are trying to put a stop to
it.


https://www.theregister.co.uk/2019/07/06/mozilla_ukisp_vallain/
  The UK ISPA earlier this week proposed Mozilla, self-styled defender
of internet freedom, as a black hat for its "proposed approach to
introduce DNS-over-HTTPS in such a way as to bypass UK filtering
obligations and parental controls, undermining internet safety
standards in the UK."

source doc for DOH protocol
  https://tools.ietf.org/html/rfc8484
  Category: Standards Track
you can skip most of it and just look at sections
  8.  Privacy Considerations
  9.  Security Considerations
 10. Operational Considerations

and also take a look at
  
https://datatracker.ietf.org/doc/draft-livingood-doh-implementation-risks-issues/?include_text=1

links to blog posts that discuss the "rights" or "wrongs" of DoH
  https://doh.defaultroutes.de/


Regards,
Lee
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to