[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-ia64-devel] [PATCH]: allow hypercalls only from kernels.

To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx, "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>, Alex Williamson <alex.williamson@xxxxxx>
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Mon, 20 Mar 2006 14:28:00 +0100
Delivery-date: Mon, 20 Mar 2006 13:25:09 +0000
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>

Hi,

this patch complete the previous one.
Hypercalls are only allowed from kernels.
I have added an 'unsafe_hypercall' boolean command line option to enable the 
two debugging hypercalls.  This option is disabled by default, as it may be 
used to write in the kernel area.

Tested by boot+shutdown of dom0+domU (option off).
Tested by boot of dom0 + postat (option on).

Tristan.

Attachment: xen-security2.diffs
Description: Text Data

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel

Follow-Ups:
- [Xen-ia64-devel] Re: [PATCH]: allow hypercalls only from kernels.
  - From: Alex Williamson

Prev by Date: Re: [Xen-ia64-devel] [RFC] The "vcpu->arch.privregs" is doubly used
Next by Date: RE: [Xen-ia64-devel] RE: [PATCH]: disable handling of legacy privified insns
Previous by thread: [Xen-ia64-devel] [PATCH]: huge security hole
Next by thread: [Xen-ia64-devel] Re: [PATCH]: allow hypercalls only from kernels.
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.