public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: RSA/SHA1-NSEC3-SHA1 signature bug?
Date: Wed, 22 Oct 2014 00:58:31 -0500	[thread overview]
Message-ID: <54474787.5010508@dailydata.net> (raw)
In-Reply-To: <1413897070.15920.102.camel@rice-oxley.tremer.info>

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

Ignore my previous e-mail. My problem is not related. It appears to be
an issue with setup not reading/writing
/var/ipfire/dns/settings.something. I'm trying to track it down.

Rod

On 10/21/2014 08:11 AM, Michael Tremer wrote:
> Hello fellow dnsmasq users,
> 
> there is a topic on the IPFire support forums I would like to point you
> to:
> 
>   http://forum.ipfire.org/index.php?topic=11726.0
> 
> It appears that dnsmasq cannot verify resource records of a
> DNSSEC-enabled domain. That domain uses RSA/SHA1-NSEC3-SHA1 for its
> signatures. Although there is some code in dnsmasq that is supposed to
> handle this, it does not verify the records correctly.
> 
> Did anyone else experience this problem? Is it a bug with dnsmasq or the
> authoritative name servers of that domain?
> 
> Best,
> -Michael
> 
> 
> 
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
> 

-- 
"Rod" Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net

  parent reply	other threads:[~2014-10-22  5:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 13:11 Michael Tremer
2014-10-22  2:50 ` R. W. Rodolico
2014-10-22  5:58 ` R. W. Rodolico [this message]
2014-10-22 12:01   ` Michael Tremer

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

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

  git send-email \
    --in-reply-to=54474787.5010508@dailydata.net \
    --to=rodo@dailydata.net \
    --cc=development@lists.ipfire.org \
    /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