Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Simon Kelley <simon@thekelleys.org.uk>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Fwd: [Dnsmasq-discuss] Testers wanted: DNSSEC.
Date: Sun, 09 Feb 2014 13:09:04 +0100	[thread overview]
Message-ID: <87ppmw7ajj.fsf@toke.dk> (raw)
In-Reply-To: <52F3A3B2.8020201@thekelleys.org.uk> (Simon Kelley's message of "Thu, 06 Feb 2014 15:01:06 +0000")

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


OK, so I've tried building dnsmasq on cerowrt, from git head. It seems
to have some trouble validating stuff:

Sun Feb  9 13:04:24 2014 daemon.info dnsmasq[6456]: forwarded mail2.tohojo.dk to 213.80.98.2
Sun Feb  9 13:04:24 2014 daemon.info dnsmasq[6456]: dnssec-query[DNSKEY] tohojo.dk to 213.80.98.2
Sun Feb  9 13:04:24 2014 daemon.info dnsmasq[6456]: dnssec-query[DS] tohojo.dk to 213.80.98.2
Sun Feb  9 13:04:24 2014 daemon.info dnsmasq[6456]: dnssec-query[DNSKEY] dk to 213.80.98.2
Sun Feb  9 13:04:24 2014 daemon.info dnsmasq[6456]: dnssec-query[DS] dk to 213.80.98.2
Sun Feb  9 13:04:24 2014 daemon.info dnsmasq[6456]: reply dk is BOGUS DS
Sun Feb  9 13:04:24 2014 daemon.info dnsmasq[6456]: validation result is BOGUS

This is with dnssec-debug turned on.

I'm not entirely sure how to go about debugging this, but FWIW this
works:

$ dig +dnssec +sigchase mail2.tohojo.dk @213.80.98.2
...snip...
;; WE HAVE MATERIAL, WE NOW DO VALIDATION
;; VERIFYING DS RRset for dk. with DNSKEY:33655: success
;; OK We found DNSKEY (or more) to validate the RRset
;; Ok, find a Trusted Key in the DNSKEY RRset: 19036
;; VERIFYING DNSKEY RRset for . with DNSKEY:19036: success

;; Ok this DNSKEY is a Trusted Key, DNSSEC validation is ok: SUCCESS


Whereas going through the dnsmasq server fails:
$ dig +dnssec +sigchase mail2.tohojo.dk @10.42.8.1
...snip...
;; WE HAVE MATERIAL, WE NOW DO VALIDATION
;; VERIFYING DS RRset for tohojo.dk. with DNSKEY:61294: success
;; OK We found DNSKEY (or more) to validate the RRset
;; Now, we are going to validate this DNSKEY by the DS
;; OK a DS valids a DNSKEY in the RRset
;; Now verify that this DNSKEY validates the DNSKEY RRset
;; VERIFYING DNSKEY RRset for dk. with DNSKEY:26887: success
;; OK this DNSKEY (validated by the DS) validates the RRset of the DNSKEYs, thus the DNSKEY validates the RRset
;; Now, we want to validate the DS :  recursive call


Launch a query to find a RRset of type DNSKEY for zone: .

;; DNSKEYset that signs the RRset to chase:
.			0	IN	DNSKEY	256 3 8 AwEAAYRU41/8smgAvuSojEP4jaj5Yll7WPaUKpYvnz2pnX2VIvRn4jsy Jns80bloenG6X9ebJVy2CFtZQLKHP8DcKmIFotdgs2HolyocY1am/+33 4RtzusM2ojkhjn1FRGtuSE9s2TSz1ISv0yVnFyu+EP/ZkiWnDfWeVrJI SEWBEr4V
.			0	IN	DNSKEY	257 3 8 AwEAAagAIKlVZrpC6Ia7gEzahOR+9W29euxhJhVVLOyQbSEW0O8gcCjF FVQUTf6v58fLjwBd0YI0EzrAcQqBGCzh/RStIoO8g0NfnfL2MTJRkxoX bfDaUeVPQuYEhg37NZWAJQ9VnMVDxP/VHL496M/QZxkjf5/Efucp2gaD X6RS6CXpoY68LsvPVjR0ZSwzz1apAzvN9dlzEheX7ICJBBtuA6G3LQpz W5hOA2hzCTMjJPJ8LbqF6dsV6DoBQzgul0sGIcGOYl7OyQdXfZ57relS Qageu+ipAdTTJ25AsRTAoub8ONGcLmqrAmRLKBP1dfwhYB4N7knNnulq QxA+Uk1ihz0=
.			0	IN	DNSKEY	256 3 8 AwEAAb8sU6pbYMWRbkRnEuEZw9NSir707TkOcF+UL1XiK4NDJOvXRyX1 95Am5dQ7bRnnuySZ3daf37vvjUUhuIWUAQ4stht8nJfYxVQXDYjSpGH5 I6Hf/0CZEoNP6cNvrQ7AFmKkmv00xWExKQjbvnRPI4bqpMwtHVzn6Wyb BZ6kuqED



Launch a query to find a RRset of type RRSIG for zone: .

;; RRSIG for DNSKEY  is missing  to continue validation : FAILED



Not really sure what to make of this?

-Toke

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2014-02-09 12:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 16:20 Dave Taht
2014-02-05  7:13 ` Toke Høiland-Jørgensen
2014-02-05 17:10   ` Toke Høiland-Jørgensen
2014-02-05 19:51     ` Simon Kelley
2014-02-05 20:09       ` Toke Høiland-Jørgensen
2014-02-05 22:26         ` Simon Kelley
2014-02-06  7:28           ` Toke Høiland-Jørgensen
2014-02-06 10:53             ` Simon Kelley
2014-02-06 10:57               ` Toke Høiland-Jørgensen
2014-02-06 11:27                 ` Simon Kelley
2014-02-06 12:35                   ` Toke Høiland-Jørgensen
2014-02-06 15:01                     ` Simon Kelley
2014-02-09 12:09                       ` Toke Høiland-Jørgensen [this message]
2014-02-09 12:23                         ` Simon Kelley
2014-02-09 12:48                           ` Toke Høiland-Jørgensen
2014-02-09 18:04                             ` Dave Taht
2014-02-09 18:47                               ` Toke Høiland-Jørgensen
2014-02-09 21:02                               ` Simon Kelley
2014-02-09 20:59                             ` Simon Kelley
2014-02-09 21:07                               ` Dave Taht
2014-02-09 21:16                                 ` Toke Høiland-Jørgensen
2014-02-09 21:33                               ` Toke Høiland-Jørgensen
2014-02-10 10:50                                 ` Simon Kelley
2014-02-10 11:39                                 ` Simon Kelley
2014-02-10 12:59                                   ` Toke Høiland-Jørgensen
2014-02-10 16:45                                     ` Simon Kelley
2014-02-10 16:59                                       ` Toke Høiland-Jørgensen
2014-02-10 17:12                                         ` Simon Kelley
2014-02-10 17:14                                         ` Dave Taht
2014-02-10 21:47                                           ` Simon Kelley
2014-02-11 11:34                                         ` Simon Kelley
2014-02-11 14:01                                           ` Toke Høiland-Jørgensen
2014-02-11 15:51                                             ` Simon Kelley
2014-02-11 16:25                                               ` Toke Høiland-Jørgensen
2014-02-06 13:42                   ` Toke Høiland-Jørgensen
2014-02-06 14:40                     ` Simon Kelley

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=87ppmw7ajj.fsf@toke.dk \
    --to=toke@toke.dk \
    --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