Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Date: Wed, 16 Dec 2020 20:38:25 +0530 (IST)
From: P J P <ppandit@...hat.com>
To: QEMU Developers <qemu-devel@...gnu.org>
cc: oss security list <oss-security@...ts.openwall.com>, 
    Daniel Berrange <berrange@...hat.com>, 
    Michael Tsirkin <mtsirkin@...hat.com>, Petr Matousek <pmatouse@...hat.com>, 
    Stefano Stabellini <sstabellini@...nel.org>, 
    Michael Roth <michael.roth@....com>
Subject: [ANNOUNCE] qemu-security mailing list

   Hello,

* QEMU project has set-up a dedicated mailing list to receive and triage all
   its security issues.

   Please see:
     -> https://www.qemu.org/contribute/security-process/
     -> https://lists.nongnu.org/mailman/listinfo/qemu-security

* If you are a security researcher OR think you've found a potential security
   issue in QEMU, please kindly follow the new process to report your issues.

* This is a moderated mailing list. It is meant for systematic handling of
   QEMU security issues and coordinate their public disclosure.

* Membership of this list is limited to people involved in the analysis and
   triage of QEMU security issues.

* To report QEMU security issues you need/should not subscribe to this list.

* We'd like to invite representatives of security teams who are downstream
   consumers of QEMU to contact the list, if they wish to participate in the
   triage process.

* All members will be required to agree and adhere to the embargo rules and
   restrictions.


Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
8685 545E B54C 486B C6EB 271E E285 8B5A F050 DE8D

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.