unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] resolv: Reject trailing characters in host names [BZ #20018]
Date: Mon, 21 Jan 2019 10:04:23 +0100	[thread overview]
Message-ID: <87o98aidpk.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <3edd9620-bedb-0d2e-c9c2-8b811141eeb4@gotplt.org> (Siddhesh Poyarekar's message of "Sat, 19 Jan 2019 21:44:09 +0530")

* Siddhesh Poyarekar:

> On 19/01/19 1:43 AM, Florian Weimer wrote:
>> This is the main patch.  I kept postponing it because it's a bit
>> involved despite how little actually changes in behavior. 8-/
>> 
>> Siddhesh, do you want this in 2.29?  I will have to request a CVE ID for
>> this, I think, and it would be nice to report the first fixed release to
>> MITRE.
>> 
>> (This needs the other two resolv patches I posted today.)
>
> I'll let this through since this is a security fix; we would have had
> this backported right after the release anyway.  I've looked at all
> three patches and the changes look fine to me with more details in the
> git commit message; the second patch for example only mentions that it's
> a precursor to this bug fix and nothing else.

I've pushed the first and second patch.  For the latter, I filed a
separate bug 24112 and explained the issue in the commit message.

I will push the fix for bug 20018 once I've got the CVE assignment
(probably later today).

Thanks,
Florian

      reply	other threads:[~2019-01-21  9:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 20:13 [PATCH] resolv: Reject trailing characters in host names [BZ #20018] Florian Weimer
2019-01-19 16:14 ` Siddhesh Poyarekar
2019-01-21  9:04   ` Florian Weimer [this message]

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://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=87o98aidpk.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.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).