Yet another Quadruple DNS?

• Subject: Yet another Quadruple DNS?
• From: bortzmeyer at nic.fr (Stephane Bortzmeyer)
• Date: Tue, 3 Apr 2018 17:04:02 +0200
• In-reply-to: <[email protected]>
• References: <CA+LTh5Ug1S[email protected]> <15[email protected]> <CA[email protected]> <CA+LTh5WfZc[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

On Tue, Apr 03, 2018 at 10:54:34AM -0400,
 Rich Kulawiec <rsk at gsp.org> wrote 
 a message of 10 lines which said:

> Watch what you wish for: you might get it.  The number of
> attack/abuse vectors (and the severity of their consequences for
> security and privacy) involved in doing auto-update may rival those
> involved in not doing auto-update.

Also, there is the risk of getting updates that will disable some
features, if there is a change in the commercial strategy of the
vendor
<https://boingboing.net/2016/09/19/hp-detonates-its-timebomb-pri.html>.
All these risks are documented in RFC 8240, a highly recommended
reading.

• References:
  • Yet another Quadruple DNS?
    • From: nop at imap.cc (nop at imap.cc)
  • Yet another Quadruple DNS?
    • From: mysidia at gmail.com (Jimmy Hess)
  • Yet another Quadruple DNS?
    • From: mehmet at akcin.net (Mehmet Akcin)
  • Yet another Quadruple DNS?
    • From: mattlists at rivervalleyinternet.net (Matt Hoppes)
  • Yet another Quadruple DNS?
    • From: list at satchell.net (Stephen Satchell)
  • Yet another Quadruple DNS?
    • From: list-nanog2 at dragon.net (Paul Ebersman)
  • Yet another Quadruple DNS?
    • From: bortzmeyer at nic.fr (Stephane Bortzmeyer)
  • Yet another Quadruple DNS?
    • From: list-nanog2 at dragon.net (Paul Ebersman)
  • Yet another Quadruple DNS?
    • From: rsk at gsp.org (Rich Kulawiec)

• Prev by Date: Yet another Quadruple DNS?
• Next by Date: From Nov 2017...
• Previous by thread: Yet another Quadruple DNS?
• Next by thread: Yet another Quadruple DNS?
• Index(es):
  • Date
  • Thread