On Sun, 2008-02-10 at 20:11 +, Samuel Thibault wrote:
> The question was rather whether the exploit was run in dom0 or in a domU
Yes. It was run in a domU. However, after upgrading to latest Xen (hg
tip), I have not been able to reproduce the crash. It happens reliably
on the Xen provided in E
William Pitcock, le Sun 10 Feb 2008 13:55:01 -0600, a écrit :
> On Sun, 2008-02-10 at 14:40 +0100, Bastian Blank wrote:
> > On Sun, Feb 10, 2008 at 06:56:59AM -0600, William Pitcock wrote:
> > > I'm sorry but I cannot provide evidence because it would involve
> > > crashing a production machine. Us
Hi,
On Sun, 2008-02-10 at 14:40 +0100, Bastian Blank wrote:
> On Sun, Feb 10, 2008 at 06:56:59AM -0600, William Pitcock wrote:
> > I'm sorry but I cannot provide evidence because it would involve
> > crashing a production machine. Users of said machine are already annoyed
> > that it crashed the f
William Pitcock, le Sun 10 Feb 2008 06:56:59 -0600, a écrit :
> On Sun, 2008-02-10 at 13:32 +0100, Bastian Blank wrote:
> > You have to show evidence that the Hypervisor crashed if the exploit
> > runs in a domU. dom0 is special and can always crash the hypervisor. A
> > stacktrace is usable to do
On Sun, Feb 10, 2008 at 06:56:59AM -0600, William Pitcock wrote:
> I'm sorry but I cannot provide evidence because it would involve
> crashing a production machine. Users of said machine are already annoyed
> that it crashed the first time.
Okay. Where did you run the exploit the first time?
> Th
Hi,
On Sun, 2008-02-10 at 13:32 +0100, Bastian Blank wrote:
> You have to show evidence that the Hypervisor crashed if the exploit
> runs in a domU. dom0 is special and can always crash the hypervisor. A
> stacktrace is usable to do this.
I'm sorry but I cannot provide evidence because it would i
tags 464969 moreinfo
thanks
On Sat, Feb 09, 2008 at 11:37:00PM -0600, William Pitcock wrote:
> When running the exploit listed in bug 464953 [1], Xen's memory state
> becomes corrupted and the hypervisor eventually crashes, taking all of
> the domU's with it. As such, this breaks operational behav
Package: xen-hypervisor-3.2-1-i386
Version: 3.2-1
Severity: critical
Tags: security
Justification: DoS of entire system regardless of privilege
When running the exploit listed in bug 464953 [1], Xen's memory state
becomes corrupted and the hypervisor eventually crashes, taking all of
the domU's wi
8 matches
Mail list logo