Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <436A4AB0.74989FF3@dessent.net>
Date: Thu, 03 Nov 2005 09:36:48 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: WINE on Cygwin
References: <SERRANOHaZVrDs9aAOP00000120 AT SERRANO DOT CAM DOT ARTIMI DOT COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Dave Korn wrote:

>   Well, how about sandboxing?  It's the ideal way to test out a virus or other
> suspect warez: run it on a virtual machine where it can't escape into your
> real one.

But WINE isn't a virtual machine, and it doesn't offer that kind of
protection.  You would need Xen / VMWare / etc for that.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/