mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "ronmacdonald@northwesternmutual.com" <ronmacdonald@northwesternmutual.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: [musl] Re: Bug in getaddrinfo causing spurious returns with wrong
Date: Mon, 18 Jul 2022 21:02:25 +0000	[thread overview]
Message-ID: <CH2PR07MB732080D747E093A1E9555026B28C9@CH2PR07MB7320.namprd07.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

Our business is being impacted by this bug submitted on Nov 2021:
https://www.openwall.com/lists/musl/2021/11/23/2

It appears the release 1.2.3 (April 7, 2022) does not contain the fix.  Is there way to find out when/if a fix would be released?


Thank you,
Ron







This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications with {SECURE MESSAGE} in the subject line have been sent using a secure messaging system. Communications that do not have this tag may not be secure and could be observed by a third party. Our commitment to privacy: At Northwestern Mutual, your privacy is important to us. For more information about our privacy practices, please review our privacy notices. 



[-- Attachment #2: Type: text/html, Size: 3291 bytes --]

             reply	other threads:[~2022-07-18 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 21:02 ronmacdonald [this message]
2022-07-19  2:48 ` Rich Felker

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=CH2PR07MB732080D747E093A1E9555026B28C9@CH2PR07MB7320.namprd07.prod.outlook.com \
    --to=ronmacdonald@northwesternmutual.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).