public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: "Cristian Rodríguez" <crrodriguez@opensuse.org>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH] resolv: set edns max buffer size to 1232
Date: Wed, 12 Apr 2023 09:40:27 -0300	[thread overview]
Message-ID: <575275d3-5088-3105-f823-fbb03956cad2@linaro.org> (raw)
In-Reply-To: <CAPBLoAfhQ6cCta9dYS-deAVcPnn-ZR6Qd=tN4c=mzQG9V4832A@mail.gmail.com>



On 11/04/23 10:43, Cristian Rodríguez via Libc-alpha wrote:
> ping? should not be a controversial thing to do. Most software out there
> already does.
> 

LGTM, although I am not really sure about the implications of this change.
The links you provided does say it is a conservative change thou.

> 
> On Wed, Apr 5, 2023 at 9:21 PM Cristian Rodríguez <crrodriguez@opensuse.org>
> wrote:
> 
>> Year 2020, Large scale DNS operators and software vendors
>> agreed to set the maximum edns buffer size to 1232.
>>
>> BIND9(1), NSD(2), unbound (3), dnsmasq etc  currently use this as
>> default, libc resolver should too.
>>
>> 1.
>> https://downloads.isc.org/isc/bind9/9.16.8/doc/arm/html/notes.html#feature-changes
>> 2. https://www.nlnetlabs.nl/news/2020/Oct/08/nsd-4.3.3-released/
>> 3. https://www.nlnetlabs.nl/news/2020/Oct/08/unbound-1.12.0-released/
>>
>> Signed-off-by: Cristian Rodríguez <crrodriguez@opensuse.org>
>> ---
>>  resolv/resolv-internal.h | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/resolv/resolv-internal.h b/resolv/resolv-internal.h
>> index c55f3c0366..c79d5f2135 100644
>> --- a/resolv/resolv-internal.h
>> +++ b/resolv/resolv-internal.h
>> @@ -67,7 +67,7 @@ enum
>>         spoofing attacks because the randomness in a DNS packet is
>>         concentrated in the first fragment (with the headers) and does
>>         not protect subsequent fragments.  */
>> -    RESOLV_EDNS_BUFFER_SIZE = 1200,
>> +    RESOLV_EDNS_BUFFER_SIZE = 1232,
>>    };
>>
>>  struct resolv_context;
>> --
>> 2.40.0
>>

  reply	other threads:[~2023-04-12 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06  1:21 Cristian Rodríguez
2023-04-11 13:43 ` Cristian Rodríguez
2023-04-12 12:40   ` Adhemerval Zanella Netto [this message]
2023-04-14 11:38     ` Adhemerval Zanella Netto
2023-04-14 16:06       ` Cristian Rodríguez

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=575275d3-5088-3105-f823-fbb03956cad2@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=crrodriguez@opensuse.org \
    --cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).