Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Dnsmasq-discuss] DNSSEC and www.ietf.org
Date: Sat, 11 Apr 2015 20:13:53 +0100	[thread overview]
Message-ID: <55297271.6040905@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw79xhodr-_npT6nPgj+x=20SNf-Br9aQYtTHo9qRHW5YA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]

On 11/04/2015 17:49, Dave Taht wrote:
> Openwrt chaos calmer trunk (latest) as of a day ago has dnsmasq 2.73rc4
> with suitable handling for DNSSEC.   Certainly I've DNSSEC enabled and
> can browse the site you mention without obvious problem.
> I stand corrected.
>
> I still would really like people to pound dnsmasq flat with
> namebench or other dns stress tests (anyone know of any? dig in a loop
> would also help), using a native ipv6 dns server upstream. It used to
> take days to trigger the bug. It may only happen on networks that have
> issues with edns0.
>
>> The automatic determination of 'valid current time' and hence checking
>> signature timestamps has an issue:  The startup script uses 'touch -t
>> 1970epoch timestampfile' to pre-create a timestamp file which slightly
>> defeats the inbuilt dnsmasq logic...not helped by the fact '-t' is an
>> invalid option.
> Well, it was a more elegant solution that dnsmasq ultimately came up
> with than what was in cerowrt, and I figure that single character fix
> is a single bug report to openwrt and patch away... if someone else
> not getting on a plane makes it.

I shall log a ticket within 48 hours, (if it doesn't get spotted and
squashed by someone else)  It's not just a case of not using '-t' but
rather of not trying to defeat the internal dnsmasq logic whilst fitting
in with the requirement of being able to create a file as 'nobody' in a
directory with a) suitable permissions and b) survives reboots, and
dealing with the new secure computing changes related to procd walled
gardens.  There are a few things pulling in opposite directions most of
which I've no clue :-)

Kevin


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4791 bytes --]

  reply	other threads:[~2015-04-11 19:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 15:52 [Cerowrt-devel] " Marc Petit-Huguenin
2015-03-30 15:58 ` Dave Taht
2015-03-30 16:19   ` David Personette
2015-03-30 17:49   ` [Cerowrt-devel] [Dnsmasq-discuss] " Simon Kelley
2015-03-30 18:17     ` Marc Petit-Huguenin
2015-03-30 18:42       ` Dave Taht
2015-04-11 15:03         ` Marc Petit-Huguenin
2015-04-11 16:32           ` Kevin Darbyshire-Bryant
2015-04-11 16:49             ` Dave Taht
2015-04-11 19:13               ` Kevin Darbyshire-Bryant [this message]
2015-04-13 14:02             ` Marc Petit-Huguenin
2015-04-11 16:38           ` Dave Taht

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=55297271.6040905@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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