A basic implementation for increased security in wine proposal

[Paul TBBle Hampson]

On Sun, Feb 01, 2009 at 01:23:49PM +0100, Guillaume SH wrote:
> Basically, yes I don't know what the exploit is (there's no magic in there :
> possibility for an exploit is enough to justify action).

So without the magic, there's no demonstrated possibility for an
exploit, so the justification goes away...

Anyway, getting some unit tests written and committed is prolly your
best way forward. Discussing behaviour is one thing, demonstrating that
it's correct and sensible is another, more effective thing.

The Wine test suite, as I understand it, is considered part of Wine's
Win32 API documentation. And it's the place to demonstrate that a given
behaviour is correct and consistent.

-- 
-----------------------------------------------------------
Paul "TBBle" Hampson, B.Sc, LPI, MCSE
Very-later-year Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
Paul.Hampson at Pobox.com

Of course Pacman didn't influence us as kids. If it did,
we'd be running around in darkened rooms, popping pills and
listening to repetitive music.
 -- Kristian Wilson, Nintendo, Inc, 1989

License: http://creativecommons.org/licenses/by/2.5/au/
-----------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20090202/c8bc7600/attachment.pgp