public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/30604] Inconsistent getaddrinfo zone-index handling
Date: Mon, 03 Jul 2023 19:08:46 +0000 [thread overview]
Message-ID: <bug-30604-131-uONBFp1u7p@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30604-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30604
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
See Also| |https://sourceware.org/bugz
| |illa/show_bug.cgi?id=20611,
| |https://sourceware.org/bugz
| |illa/show_bug.cgi?id=21657
CC| |fweimer at redhat dot com
--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
This restriction in __inet6_scopeid_pton was carried over from the previous
code in the fix for bug 20611 (commit 80d8cb91dee8bdcc4e430b3e2620d95f89b1ee0b)
and enhanced to cover more addresses in bug 21657 (commit
f768b450204f54b080ea5dc5c2071940604b424c). The original restriction goes back
to the initial change circa 2000, citing the “to follow latest RFC draft”.
We can probably drop that restriction.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-07-03 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 20:57 [Bug network/30604] New: " mirai at makinata dot eu
2023-07-03 19:08 ` fweimer at redhat dot com [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-30604-131-uONBFp1u7p@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).