[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41F35F72-E66D-49B8-BE03-CBBE71275CD0@lightwave.net.ru>
Date: Tue, 02 Jun 2026 21:14:13 +0300
From: Dan Yefihmov <dan@...htwave.net.ru>
To: oss-security@...ts.openwall.com
Subject: Re: BIRD/BIRD2: stack buffer overflow in BGP AS_PATH mask matching, CVE pending
On June 2, 2026 8:27:14 PM GMT+03:00, Stuart Henderson <stu@...cehopper.org> wrote:
>Yes, I did. That doesn't rule out things like "don't plan to fix because
>it's no longer an issue".
>
Didn't you think that in that case it's considerably more reasonable to explicitly write: "It's already fixed, and the fix will be in the next release scheduled at ..." instead of "We don't CURRENTLY plan to fix it"?
Sincerely Yours, Dan.
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
