-3

Hallo,
excuse me but automatically opening .exe with wine without confirmation from the user is plain wrong and completely lame. Today I tried to move around random files from an insecure windows machine and due to permissions I needed to run an instance of konqueror as root. Imagine my frustrations when I accidentally single clicked on one .exe and it got executed without any warning!?

Now going to check for viruses...

So what's the idea here? Issue a big warning before opening files with wine!

Konqueror ( or KDE ) simply sees "wine" as a handler for that file type. Maybe an addition could be made that says "The handling application will execute this" which could also be used for scripts, etc.

+1
(including these brackets for padding as the forum is not allowing so short messages... why!?)

avalon wrote:+1
(including these brackets for padding as the forum is not allowing so short messages... why!?)

Because of "power posting". Some only post something like +1 instead of describing in detail why they agree or not...
I think "agreed" would work normally.

bcooksley wrote:Konqueror ( or KDE ) simply sees "wine" as a handler for that file type. Maybe an addition could be made that says "The handling application will execute this" which could also be used for scripts, etc.

Like this?
I'm not really used to krita :-$ ... but X marks the spot. As I see it it's only nessesary for the first entry in the list since that's the one being automaticly executed.

In this way it would be more general, and not an ugly one of a kind fix.

Yeah, I always do this myself when I install KDE. Distributions should really be the ones to take care of this, making sure wine is automatically added as the default file handler for windows files.

Actually I see problem executing scripts without confirmation. Not that wine should or not be default.

FYI fortunately the executable didn't show to be infected (tested with updated clamav).

avalon wrote:Actually I see problem executing scripts without confirmation. Not that wine should or not be default.

FYI fortunately the executable didn't show to be infected (tested with updated clamav).

That's what I thought I see that most of user that commented this idea don't understand your idea.
You don't want that .exe are executed by wine, but that they are not or at least that there is a warning before you do that.
I would think that scripts can do more damage, as windows virus can't really do any major damage outside Wine.
Not even sure if it can do it in Wine.
I would propose to you to post another idea where KDE wouldn't automatically start scripts and similar stuff.
Also you could take a look at this thread it's somewhat related to your idea.

Primoz wrote:

avalon wrote:Actually I see problem executing scripts without confirmation. Not that wine should or not be default.

FYI fortunately the executable didn't show to be infected (tested with updated clamav).

That's what I thought I see that most of user that commented this idea don't understand your idea.
You don't want that .exe are executed by wine, but that they are not or at least that there is a warning before you do that.
I would think that scripts can do more damage, as windows virus can't really do any major damage outside Wine.
Not even sure if it can do it in Wine.
I would propose to you to post another idea where KDE wouldn't automatically start scripts and similar stuff.
Also you could take a look at this thread it's somewhat related to your idea.

Actually, Wine has become pretty good lately and a lot of viruses can actually work pretty well. I remember reading a thread somewhere where someone really got into a big mess.

Consequently, I always disallow wine from seeing anything outside its .wine directory unless I'm absolutely sure all my programs are safe. This can be done by running "winecfg" and removing all the "Drives" that point outside .wine or some directory that contains no sensitive information.