[EMAIL PROTECTED] wrote:
And I have never advocated for putting this in the registry, my
suggestion has always been to store these settings in a file outside
the .wine/drive_c jail area that is accessbile via wine's Win32 API.
Wine is *not* a sandbox. Any .exe run can make use of native (Linux)
On 2/12/07, James Hawkins <[EMAIL PROTECTED]> wrote:
On 2/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> You advocated that wine aim for working exactly like Windows, no less
> and no more, rather than deviating in user-configurable ways to
> enhance the user's control over his own syste
On 2/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
You advocated that wine aim for working exactly like Windows, no less
and no more, rather than deviating in user-configurable ways to
enhance the user's control over his own system.
Right. That's the purpose of Wine. You'd know that i
If you've read the recent mailing list posts dating up to a few weeks back I
think, there have been some cases. But like everyone said, the fact the
malware would even run in itself is almost bittersweet. It is bug-for-bug
though so you can't just do that. Possibly an 'msconfig' like thing would b
Part of my confusion what usage pattern is contracting malware on wine in
the first place
On 2/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On 2/12/07, James Hawkins <[EMAIL PROTECTED]> wrote:
> On 2/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > On 2/11/07, Misha Koshelev <[EMA
On 2/12/07, James Hawkins <[EMAIL PROTECTED]> wrote:
On 2/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On 2/11/07, Misha Koshelev <[EMAIL PROTECTED]> wrote:
> > Hi everybody,
> >
> > Thanks for your suggestions. I just posted a new patch on wine-patches
> > where I tried to incorporate t
On 2/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On 2/11/07, Misha Koshelev <[EMAIL PROTECTED]> wrote:
> Hi everybody,
>
> Thanks for your suggestions. I just posted a new patch on wine-patches
> where I tried to incorporate these and now it does the following (in
> addition to my previou
On Sun, 2007-02-11 at 23:49 -0600, John Smith wrote:
> What prevents malicious programs from writing this registry key on
> their own?
>
> On 2/11/07, Chris Robinson <[EMAIL PROTECTED]> wrote:
> On Sunday 11 February 2007 06:49:58 pm [EMAIL PROTECTED]
> wrote:
> > This soun
On Sun, 2007-02-11 at 23:49 -0600, John Smith wrote:
> What prevents malicious programs from writing this registry key on
> their own?
>
> On 2/11/07, Chris Robinson <[EMAIL PROTECTED]> wrote:
> On Sunday 11 February 2007 06:49:58 pm [EMAIL PROTECTED]
> wrote:
> > This soun
What prevents malicious programs from writing this registry key on their
own?
On 2/11/07, Chris Robinson <[EMAIL PROTECTED]> wrote:
On Sunday 11 February 2007 06:49:58 pm [EMAIL PROTECTED] wrote:
> This sounds almost perfect.
What would stop the program from adding the registry key itself when
On Sunday 11 February 2007 06:49:58 pm [EMAIL PROTECTED] wrote:
> This sounds almost perfect.
What would stop the program from adding the registry key itself when placing
the item in the startup folder, or wherever else?
> I think the counterpoint raised by James
> Hawkins would be adequately a
James Hawkins wrote:
> On 2/11/07, Misha Koshelev <[EMAIL PROTECTED]> wrote:
>> Ok, thanks to everybody's responses on the wine-devel list. Here is my
>> new version of this patch. It starts the items in the StartUp folder
>> like Windows does (again, if anybody who knows about IShellFolder will
>>
Felix Nawothnig wrote:
> [EMAIL PROTECTED] wrote:
>> This sounds almost perfect. I think the counterpoint raised by James
>> Hawkins would be adequately addressed by adding a winecfg option as
>> follows:
>
> Since we want winecfg to be gone in the long-term a registry key alone
Who said that? Or
ng-term a registry key alone
> would probably do fine.
>
> Felix
From 7465a6f5e695a33670343cd959fca3fbf763899a Mon Sep 17 00:00:00 2001
From: Misha Koshelev <[EMAIL PROTECTED]>
Date: Sun, 11 Feb 2007 21:41:51 -0600
Subject: wineboot: Start items in StartUp folder on boot, inclu
[EMAIL PROTECTED] wrote:
This sounds almost perfect. I think the counterpoint raised by James
Hawkins would be adequately addressed by adding a winecfg option as
follows:
Since we want winecfg to be gone in the long-term a registry key alone
would probably do fine.
Felix
On 2/11/07, Misha Koshelev <[EMAIL PROTECTED]> wrote:
Hi everybody,
Thanks for your suggestions. I just posted a new patch on wine-patches
where I tried to incorporate these and now it does the following (in
addition to my previous patch which just started items in the StartUp
folder):
- When w
Sun, 11 Feb 2007 15:19:46 -0600
Subject: wineboot: Start items in StartUp folder on boot, includes security
measures.
---
programs/wineboot/En.rc | 36 +++
programs/wineboot/Makefile.in |5 +
programs/wineboot/wineboot.c | 201 +
programs/w
[mailto:[EMAIL PROTECTED]
Sent: Sun 2/11/2007 4:09 PM
To: wine-devel@winehq.org
Cc: Koshelev, Misha Vladislavo
Subject: Re: wineboot: Start items in StartUp folder on boot, includes security
measures.
On 2/11/07, Misha Koshelev <[EMAIL PROTECTED]> wrote:
> Ok, thanks to everybody's re
On 2/11/07, Misha Koshelev <[EMAIL PROTECTED]> wrote:
Ok, thanks to everybody's responses on the wine-devel list. Here is my
new version of this patch. It starts the items in the StartUp folder
like Windows does (again, if anybody who knows about IShellFolder will
look over my code that would be
It seems the patch itself got lost
Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food & Drink Q&A.
http://answers.yahoo.com/dir/?link=list&sid=396545367
Hi everybody,
Thanks for your suggestions. I just posted a new patch on wine-patches
where I tried to incorporate these and now it does the following (in
addition to my previous patch which just started items in the StartUp
folder):
- When wineboot finds a file that it wants to start in the Start
21 matches
Mail list logo