WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] I/O port access permission

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] I/O port access permission
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Tue, 01 Aug 2006 17:02:26 +0200
Delivery-date: Tue, 01 Aug 2006 08:01:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Isn't it inconsistent (and perhaps to be considered a security hole)
that construct_dom0() specifically revokes access for a small group of
ports, but DOM0_IOPORT_PERMISSION blindly grants access to any ports
(including the 'special' ones) and any domain?

Thanks, Jan

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

<Prev in Thread] Current Thread [Next in Thread>