All of lore.kernel.org
 help / color / mirror / Atom feed
From: P J P <ppandit@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: peter.maydell@linaro.org,
	"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Darren Kenny" <darren.kenny@oracle.com>
Subject: Re: About 'qemu-security' mailing list
Date: Tue, 3 Nov 2020 16:48:47 +0530 (IST)	[thread overview]
Message-ID: <rrq49r0-qr6p-23o0-n1pr-364189541118@erqung.pbz> (raw)
In-Reply-To: <nycvar.YSQ.7.78.906.2010201935590.1506567@xnncv>

+-- On Tue, 20 Oct 2020, P J P wrote --+
| +-- On Fri, 16 Oct 2020, P J P wrote --+
| | * So ie. we need to:
| | 
| |   1. Create/setup a regular non-encrypted 'qemu-security' list.
| | 
| |   2. Invite representatives from user/downstream communities to subscribe to 
| |      it.
| | 
| |   3. Collect & store their PGP public keys. Also create a key for the list.
| | 
| |   4. Write 'encrypt & email' automation tool(s) to provide encryption support.
| | 
| |   5. Document and publish above details and list workflow on a page.
| | 
| | ...wdyt?
|

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



  reply	other threads:[~2020-11-03 11:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 14:20 About 'qemu-security' mailing list P J P
2020-09-11 15:27 ` Li Qiang
2020-09-11 15:40 ` Alexander Bulekov
2020-09-11 15:58   ` Alexander Bulekov
2020-09-18  7:33   ` P J P
2020-09-11 15:47 ` Daniel P. Berrangé
2020-09-11 15:51 ` Peter Maydell
2020-09-14  7:38   ` Philippe Mathieu-Daudé
2020-09-14 10:17     ` Stefan Hajnoczi
2020-09-14  8:54   ` Daniel P. Berrangé
2020-09-14  9:30     ` Peter Maydell
2020-09-14 10:15   ` Stefan Hajnoczi
2020-09-15 10:48     ` P J P
2020-09-16 11:10       ` Stefan Hajnoczi
2020-09-16 12:33         ` Peter Maydell
2020-09-16 13:06           ` Daniel P. Berrangé
2020-09-16 13:25             ` Thomas Huth
2020-09-16 13:30               ` Daniel P. Berrangé
2020-09-18  7:02         ` P J P
2020-09-30 11:46           ` P J P
2020-09-30 15:48           ` Darren Kenny
2020-10-01 10:35             ` P J P
2020-10-01 11:34               ` Darren Kenny
2020-10-01 13:57                 ` Konrad Rzeszutek Wilk
2020-10-01 18:17                 ` P J P
2020-10-16 14:17                   ` P J P
2020-10-20 14:08                     ` P J P
2020-11-03 11:18                       ` P J P [this message]
2020-11-17 14:46                     ` Stefan Hajnoczi
2020-11-17 16:19                       ` Stefan Hajnoczi
2020-11-17 16:35                         ` Daniel P. Berrangé
2020-11-18 10:32                           ` P J P

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=rrq49r0-qr6p-23o0-n1pr-364189541118@erqung.pbz \
    --to=ppandit@redhat.com \
    --cc=berrange@redhat.com \
    --cc=darren.kenny@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.