Log message:
Try CreateProcess even if SHGetFileInfo fails so that we can
launch Unix binaries.
Isn't that dangerous ?
A windows program could gain access to some commands that shouldn't
launch into normal windows.
___
Do You
Sylvain Petreolle [EMAIL PROTECTED] wrote:
Log message:
Try CreateProcess even if SHGetFileInfo fails so that we can
launch Unix binaries.
Isn't that dangerous ?
A windows program could gain access to some commands that shouldn't
launch into normal windows.
What are talking about?
On Thursday 10 October 2002 02:23 am, Sylvain Petreolle wrote:
Log message:
Try CreateProcess even if SHGetFileInfo fails so that we can
launch Unix binaries.
Isn't that dangerous ?
A windows program could gain access to some commands that shouldn't
launch into normal windows.
I will take an example : suppose you don't wan't windows programs to
have access to the network.
Today 'ping' requests doesn't work unless you're root, but the part
that detects Internet connections returns always 'LAN connection'.
With this patch, a script can ask : ping something.
Even if
Sylvain Petreolle [EMAIL PROTECTED] writes:
With this patch, a script can ask : ping something.
Even if ping.exe is not there, CreateProcess will allow /bin/ping.
This will work, as it's found and allowed for a normal unix user.
There is no way to prevent a Windows application running under
On Thu, Oct 10, 2002 at 10:30:40AM -0700, Alexandre Julliard wrote:
There is no way to prevent a Windows application running under Wine
from doing everything a Unix application could do. Even if you don't
let CreateProcess launch Unix programs the Windows app can always do a
straight system
On Thursday 10 Oct 2002 4:43 pm, Joerg Mayer wrote:
On Thu, Oct 10, 2002 at 10:30:40AM -0700, Alexandre Julliard wrote:
There is no way to prevent a Windows application running under Wine
from doing everything a Unix application could do. Even if you
don't let CreateProcess launch Unix
