;
> Anthony Liguori
>
>
> From: Michael S. Tsirkin [m...@redhat.com]
> Sent: Monday, April 28, 2014 10:53 AM
> To: Liguori, Anthony
> Cc: Peter Maydell; Anthony Liguori; qemu-devel; Stefan Hajnoczi; Andreas
> Färber
> Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: addresses fo
"Liguori, Anthony" writes:
> I think this is a bit overkill. Many projects use private mailing
> lists for this purpose.
I guess you're right on the average level of paranoia among people
willing to report security issues, but I'm afraid you might be off on
the 90th percentile.
Besides, an enc
Regards,
> >
> > Anthony Liguori
> >
> >
> > From: Michael S. Tsirkin [m...@redhat.com]
> > Sent: Monday, April 28, 2014 6:39 AM
> > To: Peter Maydell
> > Cc: Anthony Liguori; qemu-devel; Stefan Hajnoczi
day, April 28, 2014 6:39 AM
> To: Peter Maydell
> Cc: Anthony Liguori; qemu-devel; Stefan Hajnoczi; Andreas Färber; Liguori,
> Anthony
> Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: addresses for responsible
> disclosure
>
> On Mon, Apr 28, 2014 at 02:24:45PM +0100, Pet
On Mon, Apr 28, 2014 at 02:24:45PM +0100, Peter Maydell wrote:
> On 17 April 2014 19:54, Michael S. Tsirkin wrote:
> > On Thu, Apr 17, 2014 at 09:10:12AM -0700, Anthony Liguori wrote:
> >> On Thu, Apr 17, 2014 at 6:54 AM, Michael S. Tsirkin
> >> wrote:
> >> > People sometimes detect security iss
On Mon, Apr 28, 2014 at 02:24:45PM +0100, Peter Maydell wrote:
> On 17 April 2014 19:54, Michael S. Tsirkin wrote:
> > On Thu, Apr 17, 2014 at 09:10:12AM -0700, Anthony Liguori wrote:
> >> On Thu, Apr 17, 2014 at 6:54 AM, Michael S. Tsirkin
> >> wrote:
> >> > People sometimes detect security iss
On 17 April 2014 19:54, Michael S. Tsirkin wrote:
> On Thu, Apr 17, 2014 at 09:10:12AM -0700, Anthony Liguori wrote:
>> On Thu, Apr 17, 2014 at 6:54 AM, Michael S. Tsirkin wrote:
>> > People sometimes detect security issues in upstream
>> > QEMU and don't know where to report them in a non-public
On Thu, Apr 17, 2014 at 09:10:12AM -0700, Anthony Liguori wrote:
> On Thu, Apr 17, 2014 at 6:54 AM, Michael S. Tsirkin wrote:
> > People sometimes detect security issues in upstream
> > QEMU and don't know where to report them in a non-public way.
> > Of course whoever just wants full disclosure c
On Thu, Apr 17, 2014 at 09:10:12AM -0700, Anthony Liguori wrote:
> On Thu, Apr 17, 2014 at 6:54 AM, Michael S. Tsirkin wrote:
> > People sometimes detect security issues in upstream
> > QEMU and don't know where to report them in a non-public way.
> > Of course whoever just wants full disclosure c
On Thu, Apr 17, 2014 at 6:54 AM, Michael S. Tsirkin wrote:
> People sometimes detect security issues in upstream
> QEMU and don't know where to report them in a non-public way.
> Of course whoever just wants full disclosure can just go public,
> but there's nothing specified for non-public - until
On Thu, Apr 17, 2014 at 03:03:48PM +0100, Peter Maydell wrote:
> On 17 April 2014 14:54, Michael S. Tsirkin wrote:
> > People sometimes detect security issues in upstream
> > QEMU and don't know where to report them in a non-public way.
> > Of course whoever just wants full disclosure can just go
On 17 April 2014 14:54, Michael S. Tsirkin wrote:
> People sometimes detect security issues in upstream
> QEMU and don't know where to report them in a non-public way.
> Of course whoever just wants full disclosure can just go public,
> but there's nothing specified for non-public - until recently
Am 17.04.2014 15:54, schrieb Michael S. Tsirkin:
> People sometimes detect security issues in upstream
> QEMU and don't know where to report them in a non-public way.
> Of course whoever just wants full disclosure can just go public,
> but there's nothing specified for non-public - until recently A
People sometimes detect security issues in upstream
QEMU and don't know where to report them in a non-public way.
Of course whoever just wants full disclosure can just go public,
but there's nothing specified for non-public - until recently Anthony
was doing this informally.
As I started doing thi
14 matches
Mail list logo
