From: Jim Gettys <jg@freedesktop.org>
To: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Internet Service] Providers ignore routing and DNS security: experts
Date: Thu, 20 Mar 2014 12:52:19 -0400 [thread overview]
Message-ID: <CAGhGL2B90b1FUh+YhFugMkj0WyqF_-taxeH4tAHnn5iyrtjwSQ@mail.gmail.com> (raw)
In-Reply-To: <CAK-n8j6gXGnQeEk1NG+w0hEkFEkHUX5y1rpJVeYnSnqCTQU_6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On Wed, Mar 19, 2014 at 7:12 PM, Jim Reisert AD1C <jjreisert@alum.mit.edu>wrote:
> "The temporary re-routing of the network that hosts Google's public
> Domain Name System (DNS) servers shows that large parts of the
> internet are open to hijacking, with attackers easily being able to
> capture, alter and redirect traffic without users' knowledge, experts
> say."
>
>
> http://www.itnews.com.au/News/375374,providers-ignore-routing-and-dns-security-experts.aspx
I gather from folks at Google that they have been working on DNSsec for a
while. It's more complicated for Google's services than for most people.
This was from interactions before this event.
Dunno when they will start turning it on. It will be phased in across
different services at different times. I suspect this event has upped the
urgency, of course. And whether others are learning from this event is as
always unclear.
- Jim
>
> --
> Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2530 bytes --]
prev parent reply other threads:[~2014-03-20 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 23:12 Jim Reisert AD1C
2014-03-20 16:52 ` Jim Gettys [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGhGL2B90b1FUh+YhFugMkj0WyqF_-taxeH4tAHnn5iyrtjwSQ@mail.gmail.com \
--to=jg@freedesktop.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=jjreisert@alum.mit.edu \
/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