From: voices <voices@metallicrain.com>
To: xen-devel@lists.sourceforge.net
Subject: Re: Porting Openbsd to Xen?
Date: Mon, 24 Jan 2005 12:56:32 +0100 [thread overview]
Message-ID: <ct2nn1$sbk$1@sea.gmane.org> (raw)
In-Reply-To: <20050124021059.GD23571@stateless>
Nicholas Lee wrote:
> Has there been any thoughts on porting Openbsd to Xen? (http://www.cl.cam.ac.uk/Research/SRG/netos/xen/)
>
> Both Freebsd (unstable)
> http://www.bsdclusters.com/xenofreebsd/
> and Netbsd (stable)
> http://www.cl.cam.ac.uk/Research/SRG/netos/xen/faq.html#a1.3
> have been ported.
>
>
> The principle of Xen, having an insecure (linux) layer running as a host
> OS might go against the philosophy of Openbsd. It would be nice though to
> be able to use pf/altq and other Openbsd goodies in Linux land.
It would be really great, because OpenBSD has a lot of built-in security
features, for example W^X.
I think one of the biggest problems preventing usage of Xen in some
environments is lack of possibilities to highly secure guest systems -
for example great PaX (most important part of grsecurity).
We all know, that standard linux is totally defenceless against so
popular buffer overflows exploitation, or format string bugs ...
--
voices (at) metallicrain (dot) com
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-24 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 2:10 Porting Openbsd to Xen? Nicholas Lee
2005-01-24 11:56 ` voices [this message]
2005-01-25 17:32 ` David Hopwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ct2nn1$sbk$1@sea.gmane.org' \
--to=voices@metallicrain.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.