-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/03/14 14:42, Alex Xu wrote:
> On 26/03/14 10:37 AM, Nicholas Weaver wrote:
>>
>> On Mar 26, 2014, at 5:27 AM, Simon Kelley
>> wrote:
>>
>>> Signed PGP part On 25/03/14 23:03, Alex Xu wrote:
>>>
>
Poor wording on my part. I mea
On 26/03/14 10:37 AM, Nicholas Weaver wrote:
>
> On Mar 26, 2014, at 5:27 AM, Simon Kelley wrote:
>
>> Signed PGP part
>> On 25/03/14 23:03, Alex Xu wrote:
>>
>>>
>>> Poor wording on my part. I meant that `dig isc.org @74.82.42.42
>>> +dnssec` returns no results, but `dig isc.org rrsig @74.
On Mar 26, 2014, at 5:27 AM, Simon Kelley wrote:
> Signed PGP part
> On 25/03/14 23:03, Alex Xu wrote:
>
> >>
> >
> > Poor wording on my part. I meant that `dig isc.org @74.82.42.42
> > +dnssec` returns no results, but `dig isc.org rrsig @74.82.42.42`
> > does.
> >
>
> That's no good as an ups
On 26/03/14 08:27 AM, Simon Kelley wrote:
> On 25/03/14 23:03, Alex Xu wrote:
>
>>>
>
>> Poor wording on my part. I meant that `dig isc.org @74.82.42.42
>> +dnssec` returns no results, but `dig isc.org rrsig @74.82.42.42`
>> does.
>
>
> That's no good as an upstream server: you need the RRSIGs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/03/14 23:03, Alex Xu wrote:
>>
>
> Poor wording on my part. I meant that `dig isc.org @74.82.42.42
> +dnssec` returns no results, but `dig isc.org rrsig @74.82.42.42`
> does.
>
That's no good as an upstream server: you need the RRSIGs in the
On 25/03/14 06:59 PM, Simon Kelley wrote:
> On 25/03/14 22:46, Alex Xu wrote:
>> I am using the Firefox DNSSEC Validator addon, so perhaps that
>> queries in a peculiar fashion.
>
>> Dnsmasq is installed locally, only handles DNS, and has servers
>> configured through resolvconf. Servers are 8.8.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/03/14 22:46, Alex Xu wrote:
> I am using the Firefox DNSSEC Validator addon, so perhaps that
> queries in a peculiar fashion.
>
> Dnsmasq is installed locally, only handles DNS, and has servers
> configured through resolvconf. Servers are 8.8.4
I am using the Firefox DNSSEC Validator addon, so perhaps that queries
in a peculiar fashion.
Dnsmasq is installed locally, only handles DNS, and has servers
configured through resolvconf. Servers are 8.8.4.4 and 74.82.42.42. Note
that the former is DNSSEC-compliant, whereas the latter passes thro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for that. The immediate fix is obvious, but I'm not sure why
it's executing that code for that query. Could you share a little more
of your configuration? What upstream server are you using?
Thinking about this made me look at the analogous cod
*some* requests cause dnsmasq to segfault in DNSSEC code in both 2.69rc1
and git master:
Program received signal SIGSEGV, Segmentation fault.
0x0034a92934e7 in __strcpy_sse2_unaligned () from /lib64/libc.so.6
(gdb) bt
#0 0x0034a92934e7 in __strcpy_sse2_unaligned () from /lib64/libc.so.6
#
10 matches
Mail list logo
