From: Anthony Liguori <anthony@codemonkey.ws>
To: "CERT\(R\) Coordination Center" <cert@cert.org>, kvm@vger.kernel.org
Cc: "CERT\(R\) Coordination Center" <cert@cert.org>,
"Petr Matousek" <pmatouse@redhat.com>
Subject: Re: VU#976534 - How to submit security bugs?
Date: Wed, 24 Jul 2013 07:23:06 -0500 [thread overview]
Message-ID: <87fvv4gn9x.fsf@codemonkey.ws> (raw)
In-Reply-To: <201307221910.r6MJAiH7021251@eton.blue.cert.org>
"CERT(R) Coordination Center" <cert@cert.org> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Greetings,
> My name is Adam Rauf and I work for the CERT Coordination Center. We
> have a report that may affect KVM/QEMU. How can we securely send it over to
> you? Thanks so much!
For QEMU bugs, please file a bug in Launchpad and mark it as a security
bug. That will appropriately limit visibility.
http://launchpad.net/qemu
If you want to contact me directly, my public key is:
http://www.codemonkey.ws/files/aliguori.pub
You can verify that this key is what is used to sign QEMU releases at:
http://wiki.qemu.org/Download
Regards,
Anthony Liguori
>
> Adam Rauf
> Software Engineering Institute
> CERT Vulnerability Analysis Team
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
>
> iQEVAwUBUe2DstXCAanP4MNyAQI8nwf/eTb1Qox5lmgMHifDKRjj69E37FW+o5Jp
> KMIP6+IgKdWQizPctXk2Gae50a+ioaXgkCGZZ7SwNJ9iE/AX2I32QvX6pZrDCBGw
> l5Ht6UiwOLUTP3sKWO9AIYcgTDABzyNE2+bCGvDz8aqwLB8NNVqQ50f46TrQNlmB
> oiG+XzskRG0BAxKTwWc8f4v+1hdqMtp811I7XmxXkAdtlmTWPHZfPiFs0dS++Puh
> T0uLuC4nDo83hP6Yv8seMZKZZApFGfR+q4qKx7f6riNsa5v1zGgW2if++u+zRKvg
> DvjLxjtRfE9JGmCZMBcFmRJ5y4Wx/m/2wtj2+a7D/D2Hd9L5LRB0lA==
> =npI1
> -----END PGP SIGNATURE-----
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-07-24 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 18:49 VU#976534 - How to submit security bugs? CERT(R) Coordination Center
2013-07-24 7:29 ` Stefan Hajnoczi
2013-07-24 12:23 ` Anthony Liguori [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=87fvv4gn9x.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=cert@cert.org \
--cc=kvm@vger.kernel.org \
--cc=pmatouse@redhat.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.