General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: cerowrt-devel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] DNSSEC key rollover today
Date: Sun, 14 Oct 2018 08:55:39 -0700	[thread overview]
Message-ID: <CAA93jw7P=-iuWShSLQMrNA_PHrmb7pmzR=w8b=fTQUrJF2m_3A@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1810120851330.17344@uplift.swm.pp.se>

at least from where I sit, it looks like it went well.
On Thu, Oct 11, 2018 at 11:54 PM Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> On Thu, 11 Oct 2018, Dave Taht wrote:
>
> > if any of you are still using cerowrt, and dnssec, it's gonna break
> > unless you update this, or disable dnssec... I do not know if the new
> > key was in openwrt 18.06 either...
> >
> > http://www.circleid.com/posts/20181005_how_to_prepare_for_dnssec_root_ksk_rollover_on_october_11_2018/
>
> Just as an operational concern, if you have an old image of something (pre
> mid 2017) that doesn't have the new key, it's not going to be able to
> download the new key using the old key, as of today.
>
> Any old install might have the key update function implemented and might
> have the new key, but as soon as you re-install and the new key is not
> there anymore, it'll stop working.
>
> A DNSSEC validating device needs to have functionality to get the root key
> somehow and keep it updated. Otherwise it's better to just not validate at
> all if one cares about operational availability of the service.
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se



-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

      reply	other threads:[~2018-10-14 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 14:33 [Bloat] " Dave Taht
2018-10-12  6:54 ` [Bloat] [Cerowrt-devel] " Mikael Abrahamsson
2018-10-14 15:55   ` Dave Taht [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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to='CAA93jw7P=-iuWShSLQMrNA_PHrmb7pmzR=w8b=fTQUrJF2m_3A@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=swmike@swm.pp.se \
    /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