From: P J P <ppandit@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Michael Tsirkin <mtsirkin@redhat.com>, qemu-devel@nongnu.org
Subject: Re: About 'qemu-security' list subscription process
Date: Fri, 22 Jan 2021 18:43:08 +0530 (IST) [thread overview]
Message-ID: <5rqo7o5p-289n-4p99-2o3p-323o70q813r5@erqung.pbz> (raw)
In-Reply-To: <20210115181029.GY1692978@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
+-- On Fri, 15 Jan 2021, Daniel P. Berrangé wrote --+
| IOW ideally there should be some web of trust whereby some existing
| member(s) knows the person/entity who is requesting acces. Other cases would
| have to be evaluated case-by-case basis.
* True, sounds reasonable. I'll probably start a thread on the -sec list for
pending requests.
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
8685 545E B54C 486B C6EB 271E E285 8B5A F050 DE8D
prev parent reply other threads:[~2021-01-22 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 14:03 About 'qemu-security' list subscription process P J P
2021-01-15 18:10 ` Daniel P. Berrangé
2021-01-22 13:13 ` P J P [this message]
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=5rqo7o5p-289n-4p99-2o3p-323o70q813r5@erqung.pbz \
--to=ppandit@redhat.com \
--cc=berrange@redhat.com \
--cc=mtsirkin@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 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).