lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sat, 15 Aug 2015 18:41:37 +0200
From: "Stefan Kanthak" <>
To: <>
Subject: Re: [FD] Mozilla extensions: a security nightmare

"Bruce A. Peters" <> wrote:


> If they had to type in a password and were presented with a
> simple "do you want to install yayayhh.exe? (meta data) etc.)
> and an administrator password prompt, it would greatly reduce
> the chance of executing unwanted code.

No, this is wrong!

Correct is: it would reduce the chance of executing unwanted code
WITH administrative rights.

Execution of unwanted code with their own user rights is but NOT
controlled/restricted by UAC.


| One of the common misconceptions about UAC and about Same-desktop
| Elevation in particular is that it prevents malware from being
| installed or from gaining administrative rights. First, malware
| can be written not to require administrative rights, and malware
| can be written to write just to areas in the user's profile. More
| important, Same-desktop Elevation in UAC is not a security boundary
| and can be hijacked by unprivileged software that runs on the same
| desktop. Same-desktop Elevation should be considered a convenience
| feature, and from a security perspective, "Protected Administrator"
| should be considered the equivalent of "Administrator." By contrast,
| using Fast User Switching to log on to a different session by using
| an administrator account involves a security boundary between the
| administrator account and the standard user session.

Also see

To restrict or inhibit execution of unwanted code you have to setup
SAFER a.k.a. software restriction policies (which are available
since FOURTEEN long years now).
See <> or for example.

> Microsoft doesn't do this because they know that people will
> bitch and complain. I say let them bitch and complain. 

Despite Microsofts bad habit to create (nowadays) "protected"
Administrator accounts during Windows setup they clearly advise
their users to create and use "standard user" accounts where UAC
operates the way you request!


| There are three types of accounts. Each type gives you a different
| level of control over the PC:
| * Administrator accounts provide the most control over a PC, and
|   should be used sparingly. You probably created this type of
|   account when you first started using your PC.
| * Standard accounts are for everyday use. If you're setting up
|   accounts for other people on your PC, it's a good idea to give
|   them standard accounts.
| * Child accounts are useful for parents who want to monitor or set
|   limits on their child's PC use, with the Family Safety settings
|   in Windows. For more info about Family Safety, see
|   Set up Family Safety.

JFTR: the default account type for user accounts created after setup
      is "standard user"!


| When you set up Windows, you were required to create a user account.
| This account is an administrator account that allows you to set up
| your computer and install any programs that you'd like to use.
| Once you finish setting up your computer, we recommend that you
| create a standard account and use it for your everyday computing.
| If you create new user accounts, you should also make them standard
| accounts. Using standard accounts will help keep your computer more
| secure.

stay tuned

PS: I consider top posting and full quotes as an equally bad habit!

Powered by blists - more mailing lists