site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Share Topic
Posting?
Post a:
Post a:
Links: ·Hijack This logs? ·Panda Free Tools ·Vundo Removal
AuthorAll Replies

OZO
Premium
join:2003-01-17
kudos:2

reply to mysec

Re: Blocking AutoRun - Re-visited

Let's make it simple - there should be no way to automatically execute an application from any attached media without explicit user's consent (AutoRun functionality) and there should be no any exception. Period.

If you allow such execution - you facilitate compromising computers. Isn't that simple?

Now, with current implementation of this functionality in WXP SP2 there is no way to execute AutoRun automatically in case if you block it with NoDriveAutoRun or NoDriveTypeAutoRun registry values. But there are cases of deceptive executions that may be done by users. For example:
1) Go to Start|My Computer and click on drive with attached media. Instead of opening its content in explorer (as one may expect) - you execute a startup application immediately.
2) If autorun.inf file contains 'shell\..' instructions replacing Open and/or Explore menu item(s) in context menu for new drive - you may execute a startup application from context menu instead of opening or exploring content of the drive.
No any prompt or warning will be displayed to the user in such cases. It's dangerously wrong and must be fixed ASAP.

Solution should be simple - every time AutoRun instruction is about to be executed (in two cases described above) there should be a dialog box asking for explicit permission to do so. It's imperative that it should be done without any exception. Dialog box should display explicit name of a program that is asking for permission to run.

Please note: in this post I'm talking about particular AutoRun functionality, and not about AutoPlay functionality, which is different one.
--
Keep it simple, it'll become complex by itself...


Vistaluvr

@rr.com


autoplay...
said by OZO:

Let's make it simple - there should be no way to automatically execute an application from any attached media without explicit user's consent (AutoRun functionality) and there should be no any exception. Period.

If you allow such execution - you facilitate compromising computers. Isn't that simple?

Now, with current implementation of this functionality in WXP SP2 there is no way to execute AutoRun automatically in case if you block it with NoDriveAutoRun or NoDriveTypeAutoRun registry values. But there are cases of deceptive executions that may be done by users. For example:
1) Go to Start|My Computer and click on drive with attached media. Instead of opening its content in explorer (as one may expect) - you execute a startup application immediately.
2) If autorun.inf file contains 'shell\..' instructions replacing Open and/or Explore menu item(s) in context menu for new drive - you may execute a startup application from context menu instead of opening or exploring content of the drive.
No any prompt or warning will be displayed to the user in such cases. It's dangerously wrong and must be fixed ASAP.

Solution should be simple - every time AutoRun instruction is about to be executed (in two cases described above) there should be a dialog box asking for explicit permission to do so. It's imperative that it should be done without any exception. Dialog box should display explicit name of a program that is asking for permission to run.

Please note: in this post I'm talking about particular AutoRun functionality, and not about AutoPlay functionality, which is different one.
Solution is Vista... AND which is why UAC prompts is there

OZO
Premium
join:2003-01-17
kudos:2

Actually, it's AutoPlay, not UAC prompt



Vistaluvr

@rr.com

Actually, I am talking about this: No any prompt or warning will be displayed to the user in such cases. It's dangerously wrong and must be fixed ASAP.

If a software wants access to system directories/files, you'll get a UAC prompt is what I am saying


OZO
Premium
join:2003-01-17
kudos:2

As you may have already noticed life is full of tradeoffs. Your solution may work for Vista, but the price of this is - you are prompted so many times and so often (running applications and tools located on your computer), so eventually you'll get relaxed with confirming to UAC requests. It becomes quite annoying to enter your very simple (otherwise you'll get tired even more quickly) password. Those two factors make it less secure.

In this thread we're discussing only specific issue with automatic execution of startup application coming with unknown media. It should not be allowed in the first place. But currently it's done the way that allows un-noticed compromise of Windows computers. And that requires an immediate fix.



Vistaluvr

@rr.com

reply to OZO

Re: Blocking AutoRun - Re-visited

Bleh, it's no wonder people are getting wrong ideas.

Sunday, 03-Jun 15:38:47 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics