public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>
Cc: libc-alpha@sourceware.org,  fweimer@redhat.com,  carlos@redhat.com
Subject: Re: [PATCH] getaddrinfo: Fix use after free in getcanonname (CVE-2023-4806)
Date: Wed, 13 Sep 2023 21:03:39 +0200	[thread overview]
Message-ID: <87h6nxuc8k.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20230913173638.3067388-1-siddhesh@sourceware.org> (Siddhesh Poyarekar's message of "Wed, 13 Sep 2023 13:36:37 -0400")

* Siddhesh Poyarekar:

> diff --git a/nss/tst-nss-gai-hv2-canonname.root/etc/hosts b/nss/tst-nss-gai-hv2-canonname.root/etc/hosts
> new file mode 100644
> index 0000000000..6df862c929
> --- /dev/null
> +++ b/nss/tst-nss-gai-hv2-canonname.root/etc/hosts
> @@ -0,0 +1,64262 @@
> +ff01::ff02:ff03:2:2	test.example.com

Please generate this file during the test.  We don't need to ship it
pre-generated.  This will likely need a postclean.req file.

  reply	other threads:[~2023-09-13 19:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 17:36 Siddhesh Poyarekar
2023-09-13 19:03 ` Florian Weimer [this message]
2023-09-13 20:56 ` [PATCH v2] " Siddhesh Poyarekar
2023-09-14  8:37   ` Andreas Schwab
2023-09-14  9:48     ` Siddhesh Poyarekar
2023-09-14  9:55       ` Andreas Schwab
2023-09-14  9:57         ` Siddhesh Poyarekar
2023-09-14 10:00           ` Andreas Schwab
2023-09-14 10:06             ` Siddhesh Poyarekar
2023-09-14 10:12               ` Andreas Schwab
2023-09-14 10:24                 ` Siddhesh Poyarekar
2023-09-14 10:13 ` [PATCH v3] " Siddhesh Poyarekar
2023-09-14 10:53   ` Florian Weimer
2023-09-14 11:27     ` Siddhesh Poyarekar
2023-09-14 22:52   ` Carlos O'Donell
2023-09-15 18:41 ` [COMMITTED] " Siddhesh Poyarekar

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=87h6nxuc8k.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@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).