Networking+wine
Michael Stefaniuc
mstefani at redhat.com
Mon Mar 19 07:56:34 CDT 2012
On 03/19/2012 01:40 PM, prateek papriwal wrote:
> http://wiki.winehq.org/FAQ#head-f566a12c806a1eacaeefb7cb6419a513a773c571 as
> mentioned wine does not provide sandboxing at all but there can be some
> wine users would like to prevent Windows apps from accessing unix system
> so there is need for a simple sandboxing interface.
Like the FAQ says use SELinux or AppArmor for that. There is no way that
Wine can prevent that as the Windows apps can just call into a Linux lib
or even perform a direct system call. Or just remove the Z: drive in
winecfg as a poor men "sandboxing".
> On Mon, Mar 19, 2012 at 1:57 PM, Austin English <austinenglish at gmail.com
> <mailto:austinenglish at gmail.com>> wrote:
>
> On Mon, Mar 19, 2012 at 01:19, prateek papriwal
> <papriwalprateek at gmail.com <mailto:papriwalprateek at gmail.com>> wrote:
> > Networking + wine (like as running uTorrent in ubuntu) can be very
> > dangerous. I feel there should be some sandboxing(as in Windows)
> to prevent
> > frequent attacks. I would be very interested in implementing
> sandboxing for
> > running Wine applications.
>
> What sandboxing are you referring to in Windows?
>
> Regarding sandboxing Wine itself, see the FAQ entry:
> http://wiki.winehq.org/FAQ#head-f566a12c806a1eacaeefb7cb6419a513a773c571
>
bye
michael
More information about the wine-devel
mailing list