Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231003214424.prarc3aboi3ar7zk@yuggoth.org>
Date: Tue, 3 Oct 2023 21:44:24 +0000
From: Jeremy Stanley <fungi@...goth.org>
To: oss-security@...ts.openwall.com
Subject: Re: Xen Security Advisory 439 v1 (CVE-2023-20588) -
 x86/AMD: Divide speculative information leak

On 2023-10-03 22:37:08 +0100 (+0100), Andrew Cooper wrote:
[...]
> If you have a proposal for how you'd prefer it to be done, I'll see what
> I can do.  Perhaps BCC oss-security, or just send out a second mail?

When I send advisories, I prepare two basically identical E-mail
messages: one to the project's announcement list and one to
oss-security (signing both of them). It seems like this is the most
common approach to avoiding cross-posting between lists.
-- 
Jeremy Stanley

Download attachment "signature.asc" of type "application/pgp-signature" (964 bytes)

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.