Re: [Xen-devel] XSM permissive by default.

2016-04-05 Thread Jan Beulich
>>> On 04.04.16 at 19:12, wrote: > Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] XSM permissive by default."): >> I presume this patch would be to folks +1: >> >> From 3373a50f386b41eea6ecede4b430e4fa09b2fe7e Mon Sep 17 00:00:00 2001 >> From: Konra

Re: [Xen-devel] XSM permissive by default.

2016-04-04 Thread Ian Jackson
Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] XSM permissive by default."): > I presume this patch would be to folks +1: > > From 3373a50f386b41eea6ecede4b430e4fa09b2fe7e Mon Sep 17 00:00:00 2001 > From: Konrad Rzeszutek Wilk > Date: Thu, 10 Mar 2016 12:05:29 -0500 >

Re: [Xen-devel] XSM permissive by default.

2016-03-10 Thread Andrew Cooper
On 10/03/16 17:10, Konrad Rzeszutek Wilk wrote: > I presume this patch would be to folks +1: > > From 3373a50f386b41eea6ecede4b430e4fa09b2fe7e Mon Sep 17 00:00:00 2001 > From: Konrad Rzeszutek Wilk > Date: Thu, 10 Mar 2016 12:05:29 -0500 > Subject: [PATCH] flask: By default be in FLASK_BOOTPARAM_E

Re: [Xen-devel] XSM permissive by default.

2016-03-10 Thread Doug Goldstein
On 3/10/16 11:10 AM, Konrad Rzeszutek Wilk wrote: > On Wed, Mar 09, 2016 at 08:40:05PM -0600, Doug Goldstein wrote: >> On 3/9/16 4:09 PM, Daniel De Graaf wrote: >>> On 03/09/2016 04:17 PM, Konrad Rzeszutek Wilk wrote: On Wed, Mar 09, 2016 at 01:24:15PM +, Andrew Cooper wrote: > On 09/0

Re: [Xen-devel] XSM permissive by default.

2016-03-10 Thread Konrad Rzeszutek Wilk
On Wed, Mar 09, 2016 at 08:40:05PM -0600, Doug Goldstein wrote: > On 3/9/16 4:09 PM, Daniel De Graaf wrote: > > On 03/09/2016 04:17 PM, Konrad Rzeszutek Wilk wrote: > >> On Wed, Mar 09, 2016 at 01:24:15PM +, Andrew Cooper wrote: > >>> On 09/03/16 01:51, Konrad Rzeszutek Wilk wrote: > Hey,

Re: [Xen-devel] XSM permissive by default.

2016-03-09 Thread Doug Goldstein
On 3/9/16 4:09 PM, Daniel De Graaf wrote: > On 03/09/2016 04:17 PM, Konrad Rzeszutek Wilk wrote: >> On Wed, Mar 09, 2016 at 01:24:15PM +, Andrew Cooper wrote: >>> On 09/03/16 01:51, Konrad Rzeszutek Wilk wrote: Hey, I was wondering if it we should change the default flask_bootpar

Re: [Xen-devel] XSM permissive by default.

2016-03-09 Thread Daniel De Graaf
On 03/09/2016 04:17 PM, Konrad Rzeszutek Wilk wrote: On Wed, Mar 09, 2016 at 01:24:15PM +, Andrew Cooper wrote: On 09/03/16 01:51, Konrad Rzeszutek Wilk wrote: Hey, I was wondering if it we should change the default flask_bootparam option from permissive to disabled? The reason being is t

Re: [Xen-devel] XSM permissive by default.

2016-03-09 Thread Konrad Rzeszutek Wilk
On Wed, Mar 09, 2016 at 01:24:15PM +, Andrew Cooper wrote: > On 09/03/16 01:51, Konrad Rzeszutek Wilk wrote: > > Hey, > > > > I was wondering if it we should change the default flask_bootparam > > option from permissive to disabled? > > > > The reason being is that I was startled to see that my

Re: [Xen-devel] XSM permissive by default.

2016-03-09 Thread Andrew Cooper
On 09/03/16 01:51, Konrad Rzeszutek Wilk wrote: > Hey, > > I was wondering if it we should change the default flask_bootparam > option from permissive to disabled? > > The reason being is that I was startled to see that my xSplice > code was able to patch the hypervisor from within an PV guest! > >

Re: [Xen-devel] XSM permissive by default.

2016-03-08 Thread Doug Goldstein
On 3/8/16 7:51 PM, Konrad Rzeszutek Wilk wrote: > Hey, > > I was wondering if it we should change the default flask_bootparam > option from permissive to disabled? > > The reason being is that I was startled to see that my xSplice > code was able to patch the hypervisor from within an PV guest! >

[Xen-devel] XSM permissive by default.

2016-03-08 Thread Konrad Rzeszutek Wilk
Hey, I was wondering if it we should change the default flask_bootparam option from permissive to disabled? The reason being is that I was startled to see that my xSplice code was able to patch the hypervisor from within an PV guest! Further testing showed that I could do 'xl debug-keys R' from