Re: [MacGroup] Announcing 1.1.1.1: the fastest, privacy-first consumer DNS service

2018-04-02 Thread jansidea 
Hello group
I have not posted items in awhile and have forgotten to create my own post. So 
I am tacking onto this one. Sorry.
I have an old mac 6500, and wondering what to do with it or could someone use 
it.
Thanks
Jan



-Original Message-
From: Ed Wiser <wisero...@gmail.com>
To: Macintosh topics <macgroup@erdos.math.louisville.edu>
Sent: Sun, Apr 1, 2018 8:04 pm
Subject: [MacGroup] Announcing 1.1.1.1: the fastest, privacy-first consumer DNS 
service




https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.cloudflare.com_announcing-2D_=DwIFaQ=OAG1LQNACBDguGvBeNj18Swhr9TMTjS-x4O_KuapPgY=F2GFXrjLFqVo3VwvIlo_XYeEiRRjHv15rxcenz7A21woG2aFGcrzndoSsskxfmOs=xKvgcPa9UKGY0wmrlYHlBLtwYDny6EAg32bCVVz9D6Q=cOkvkTwNv13EbBMfIUhqupT1KBJljDLmUl6L0XGMDk0=



Announcing 1.1.1.1: the fastest, privacy-first consumer DNS service
Matthew Prince01 Apr 2018
Cloudflare's mission is to help build a better Internet. We're excited today to 
take another step toward that mission with the launch of 1.1.1.1 — the 
Internet's fastest, privacy-first consumer DNS service. This post will talk a 
little about what that is and a lot about why we decided to do it. (If you're 
interested in the technical details on how we built the service, check out 
Ólafur Guðmundsson's accompanying post.)
Quick Primer On DNS
DNS is the directory of the Internet. Whenever you click on a link, send an 
email, open a mobile app, often one of the first things that has to happen is 
your device needs to look up the address of a domain. There are two sides of 
the DNS network: Authoritative (the content side) and Resolver (the consumer 
side).
Every domain needs to have an Authoritative DNS provider. Cloudflare, since our 
launch in September 2010, has run an extremely fast and widely-used 
Authoritative DNS service. 1.1.1.1 doesn't (directly) change anything about 
Cloudflare's Authoritative DNS service.
On the other side of the DNS system are resolvers. Every device that connects 
to the Internet needs a DNS resolver. By default, these resolvers are 
automatically set by whatever network you're connecting to. So, for most 
Internet users, when they connect to an ISP, or a coffee shop wifi hot spot, or 
a mobile network then the network operator will dictate what DNS resolver to 
use.
DNS's Privacy Problem
The problem is that these DNS services are often slow and not privacy 
respecting. What many Internet users don't realize is that even if you're 
visiting a website that is encrypted — has the little green lock in your 
browser — that doesn't keep your DNS resolver from knowing the identity of all 
the sites you visit. That means, by default, your ISP, every wifi network 
you've connected to, and your mobile network provider have a list of every site 
you've visited while using them.
Network operators have been licking their chops for some time over the idea of 
taking their users' browsing data and finding a way to monetize it. In the 
United States, that got easier a year ago when the Senate voted to eliminate 
rules that restricted ISPs from selling their users' browsing data. With all 
the concern over the data that companies like Facebook and Google are 
collecting on you, it worries us to now add ISPs like Comcast, Time Warner, and 
AT to the list. And, make no mistake, this isn't a US-only problem — ISPs 
around the world see the same privacy-invading opportunity.
DNS's Censorship Problem
But privacy concerns extend far beyond just ad targeting. Cloudflare operates 
Project Galileo to protect at no cost politically or artistically important 
organizations around the world from cyber attack. Through the project we 
protect groups like LGBTQ organizations targeted in the Middle East, 
journalists covering political corruption in Africa, human rights workers in 
Asia, and bloggers on the ground covering the conflict in Crimea. We're really 
proud of the project and we're really good at stopping cyber attacks launched 
at its participants.
But it's been depressing to us to watch all too frequently how DNS can be used 
as a tool of censorship against many of the groups we protect. While we're good 
at stopping cyber attacks, if a consumer's DNS gets blocked there's been 
nothing we could do to help.


In March 2014, for instance, the government of Turkey blocked Twitter after 
recordings showing a government corruption scandal leaked online. The Internet 
was censored by the country's ISP's DNS resolvers blocking DNS requests for 
twitter.com. People literally spray painted 8.8.8.8, the IP of Google's DNS 
resolver service, on walls to help fellow Turks get back online. Google's DNS 
resolver is great, but diversity is good and we thought we could do even better.
Building a Consumer DNS Service
The insecurity of the DNS infrastructure struck the team at Cloudflare as a bug 
at the core of the Internet, so we set out to do something about it. Given we 
run one of the largest, most interconnected global networks — an

Re: [MacGroup] Announcing 1.1.1.1: the fastest, privacy-first consumer DNS service

2018-04-01 Thread Lee Larson 
On Apr 1, 2018, at 8:04 PM, Ed Wiser > wrote:

> https://blog.cloudflare.com/announcing-/ 
> 


The DNS I’ve been using for quite a while is Quad9  
(9.9.9.9). It’s wicked fast because they have dozens of servers distributed all 
over. It’s backed by IBM and a bunch of well-known Internet groups. They also 
claim an emphasis on privacy, unlike Google (8.8.8.8).

OpenDNS  is also quite fast 
and has the option of turning on child-friendly mode.

---
‌Lee Larson‌
‌leelar...@me.com ‌

‌I love deadlines. I like the whooshing sound they make as they fly by. ‌— 
Douglas Adams
‌‌

‌‌‌








signature.asc
Description: Message signed with OpenPGP
___
MacGroup mailing list
Posting address: MacGroup@erdos.math.louisville.edu
Archive: 
Answers to questions:

[MacGroup] Announcing 1.1.1.1: the fastest, privacy-first consumer DNS service

2018-04-01 Thread Ed Wiser 

https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.cloudflare.com_announcing-2D_=DwIFaQ=OAG1LQNACBDguGvBeNj18Swhr9TMTjS-x4O_KuapPgY=F2GFXrjLFqVo3VwvIlo_XYeEiRRjHv15rxcenz7A21woG2aFGcrzndoSsskxfmOs=DwYi2adPi_pWiJFnOtZ5ano6tJYaPnN6ubj9h9oSZwI=7vrpOqot0Rs6Pu2gJDGUdJPOGISC17HlsYUtjsMLFzk=

Announcing 1.1.1.1: the fastest, privacy-first consumer DNS service
Matthew Prince01 Apr 2018
Cloudflare's mission is to help build a better Internet. We're excited today to 
take another step toward that mission with the launch of 1.1.1.1 — the 
Internet's fastest, privacy-first consumer DNS service. This post will talk a 
little about what that is and a lot about why we decided to do it. (If you're 
interested in the technical details on how we built the service, check out 
Ólafur Guðmundsson's accompanying post.)

Quick Primer On DNS

DNS is the directory of the Internet. Whenever you click on a link, send an 
email, open a mobile app, often one of the first things that has to happen is 
your device needs to look up the address of a domain. There are two sides of 
the DNS network: Authoritative (the content side) and Resolver (the consumer 
side).

Every domain needs to have an Authoritative DNS provider. Cloudflare, since our 
launch in September 2010, has run an extremely fast and widely-used 
Authoritative DNS service. 1.1.1.1 doesn't (directly) change anything about 
Cloudflare's Authoritative DNS service.

On the other side of the DNS system are resolvers. Every device that connects 
to the Internet needs a DNS resolver. By default, these resolvers are 
automatically set by whatever network you're connecting to. So, for most 
Internet users, when they connect to an ISP, or a coffee shop wifi hot spot, or 
a mobile network then the network operator will dictate what DNS resolver to 
use.

DNS's Privacy Problem

The problem is that these DNS services are often slow and not privacy 
respecting. What many Internet users don't realize is that even if you're 
visiting a website that is encrypted — has the little green lock in your 
browser — that doesn't keep your DNS resolver from knowing the identity of all 
the sites you visit. That means, by default, your ISP, every wifi network 
you've connected to, and your mobile network provider have a list of every site 
you've visited while using them.

Network operators have been licking their chops for some time over the idea of 
taking their users' browsing data and finding a way to monetize it. In the 
United States, that got easier a year ago when the Senate voted to eliminate 
rules that restricted ISPs from selling their users' browsing data. With all 
the concern over the data that companies like Facebook and Google are 
collecting on you, it worries us to now add ISPs like Comcast, Time Warner, and 
AT to the list. And, make no mistake, this isn't a US-only problem — ISPs 
around the world see the same privacy-invading opportunity.

DNS's Censorship Problem

But privacy concerns extend far beyond just ad targeting. Cloudflare operates 
Project Galileo to protect at no cost politically or artistically important 
organizations around the world from cyber attack. Through the project we 
protect groups like LGBTQ organizations targeted in the Middle East, 
journalists covering political corruption in Africa, human rights workers in 
Asia, and bloggers on the ground covering the conflict in Crimea. We're really 
proud of the project and we're really good at stopping cyber attacks launched 
at its participants.

But it's been depressing to us to watch all too frequently how DNS can be used 
as a tool of censorship against many of the groups we protect. While we're good 
at stopping cyber attacks, if a consumer's DNS gets blocked there's been 
nothing we could do to help.



In March 2014, for instance, the government of Turkey blocked Twitter after 
recordings showing a government corruption scandal leaked online. The Internet 
was censored by the country's ISP's DNS resolvers blocking DNS requests for 
twitter.com. People literally spray painted 8.8.8.8, the IP of Google's DNS 
resolver service, on walls to help fellow Turks get back online. Google's DNS 
resolver is great, but diversity is good and we thought we could do even better.

Building a Consumer DNS Service

The insecurity of the DNS infrastructure struck the team at Cloudflare as a bug 
at the core of the Internet, so we set out to do something about it. Given we 
run one of the largest, most interconnected global networks — and have a lot of 
experience with DNS — we were well positioned to launch a consumer DNS service. 
We began testing and found that a resolver, running across our global network, 
outperformed any of the other consumer DNS services available (including 
Google's 8.8.8.8). That was encouraging.

We began talking with browser manufacturers about what they would want from a 
DNS resolver. One word kept coming up: privacy. Beyond just a commitment not to 
use browsing data to help