Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Simon Kelley <simon@thekelleys.org.uk>
Cc: dnsmasq-discuss <Dnsmasq-discuss@lists.thekelleys.org.uk>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Dnsmasq-discuss]  test-ipv6.com vs dnssec
Date: Mon, 28 Apr 2014 12:07:06 -0700	[thread overview]
Message-ID: <CAA93jw66ZC14u88jOgFOhbj-QQgNVfZSZnxWTTRBVLNSEx8ZAQ@mail.gmail.com> (raw)
In-Reply-To: <535AAE37.103@thekelleys.org.uk>

On Fri, Apr 25, 2014 at 11:49 AM, Simon Kelley <simon@thekelleys.org.uk> wrote:
> On 25/04/14 19:01, Jim Gettys wrote:
>> More specifically, after boot, most of the time test-ipv6.com reports lots
>> of problems.
>>
>> Then I turned off both dnssec and dnssec-check-unsigned, and restarted
>> dnsmasq; clean bill of health from test-ipv6.com.
>>
>> Then I turned on dnssec only, leaving dnssec-check-unsigned, and got a
>> clean bill of health.
>>
>> Then I turned on both at the same time, and things are working.
>>
>> So we seem to have a boot time race of some sort.
>>                               - Jim
>>
>>
>
>
> test-ipv6.com is unsigned, so the important thing which is likely
> failing is the query for the DS record of test-ipv6.com, which should
> return NSEC records providing it doesn't exist, signed by .com

As one example of a registrar not with the program, name.com
(registrar for bufferbloat.net) does not allow for ds records to
come from it, so that domain can't be fully signed.

So it sounds to me as if negative proofs are not possible with
registrars that lack this support?

>
> Simon.
>
>
>
>>
>> On Fri, Apr 25, 2014 at 1:39 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>>> jg tells me the test-ipv6.com site fails with dnssec and enabled on
>>> native ipv6.
>>>
>>> disabling dnssec works.
>>>
>>> anyone can confirm? get a log/packet capture?
>>>
>>>
>>> --
>>> Dave Täht
>>> _______________________________________________
>>> Cerowrt-devel mailing list
>>> Cerowrt-devel@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>>
>>
>>
>>
>> _______________________________________________
>> Dnsmasq-discuss mailing list
>> Dnsmasq-discuss@lists.thekelleys.org.uk
>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>>
>



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

  parent reply	other threads:[~2014-04-28 19:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 17:39 [Cerowrt-devel] " Dave Taht
2014-04-25 18:01 ` Jim Gettys
2014-04-25 18:45   ` James Cloos
2014-04-25 18:49   ` [Cerowrt-devel] [Dnsmasq-discuss] " Simon Kelley
2014-04-25 19:43     ` Török Edwin
2014-04-25 19:48       ` Török Edwin
2014-04-28 19:07     ` Dave Taht [this message]
2014-04-28 19:57       ` James Cloos
2014-04-28 20:17         ` Török Edwin
2014-04-30 21:44           ` James Cloos
2014-04-25 19:24   ` [Cerowrt-devel] " Török Edwin
2014-04-25 19:42     ` Dave Taht
2014-04-26 19:41       ` Sebastian Moeller
2014-04-27 16:15         ` Dave Taht
2014-04-27 19:49           ` Sebastian Moeller

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=CAA93jw66ZC14u88jOgFOhbj-QQgNVfZSZnxWTTRBVLNSEx8ZAQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=Dnsmasq-discuss@lists.thekelleys.org.uk \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=simon@thekelleys.org.uk \
    /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