Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

"Very Severe Hole" In Vista UAC Design

Posted by kdawson on Tue Feb 13, 2007 04:07 PM
from the she-said-he-said dept.
Cuts and bruises writes "Hacker Joanna Rutkowska has flagged a "very severe hole" in the design of Windows Vista's User Account Controls (UAC) feature. The issue is that Vista automatically assumes that all setup programs (application installers) should be run with administrator privileges — and gives the user no option to let them run without elevated privileges. This means that a freeware Tetris installer would be allowed to load kernel drivers. Microsoft's Mark Russinovich acknowledges the risk factor but says it was a 'design choice' to balance security with ease of use."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by KingSkippus (799657) * on Tuesday February 13 2007, @04:08PM (#18003076) Homepage Journal

    There's a much, much bigger hole than any programmer could possibly exploit: The annoyance factor.

    Last night, I restored my old XP partition after figuring I'd give Vista a shot for just a couple of days. You know, just to experience it myself instead of taking other people's word for what it's like.

    The theme of Vista seems to be simple: Annoy the hell out of he end user. You want to run an application, is that okay? You want to copy a file, is that okay? You want to change your desktop background, is that okay? You want to copy text from IE7, is that okay? You want to delete an old text file, is that okay? You want to paste text into a form field in IE7, is that okay? The list goes on and on. Almost every action in Vista is actually compose of two separate actions: the one you want to do, and the confirmation to do it.

    After getting Windows Vista installed, I took an hour or so to configure my personal settings and install a couple of applications. I had to acknowledge somewhere between 50 and 100 dialog boxes asking me if it was okay to do what I was doing. No, I'm not exaggerating.

    Now, I'm a very experienced computer user, and I've worked for over a decade supporting PCs, servers, networks, and so on. Yes, I know, I could disable UAC if I want to, but that kind of defeats the point of Vista's so-called beefed up security.

    Even I became so numb to clicking OK in two short days that I wouldn't think twice about it. You want to move that shortcut on your start menu, is that okay? You want to install the Pwnzjoo virus, is that okay? You want to send your bank account numbers to Nigeria, is that okay? Yes, yes, yes, dammit!

    If Microsoft wants to really get serious about security, they have to get it through their heads that it's not about locking everything down and popping up prompt after prompt after prompt to the user. It's about being smart, letting the user do normal things without interference or interruption, and having the level of alerts match the danger of what's being done.

    As it is, Vista cries wolf so often that when the real wolves show up, I'd be surprised if any user, newbie or guru, listens.

    • by dotpavan (829804) on Tuesday February 13 2007, @04:13PM (#18003166) Homepage
      offtopic, yet:

      no doubt, thats why Dell is marketing its harware for Vista as great for "booting the OS, w/o running apps or games [googlepages.com]" (link via this [dell.com])

      Since when did booting an OS become a "feature" of the OS?

    • by CheeseburgerBrown (553703) on Tuesday February 13 2007, @04:16PM (#18003226) Homepage Journal
      I think you're right. Microsoft has failed to appreciate the user psychology of interacting with authorization prompts in a way that would shame most retarded chimpanzees. The only explanation that doesn't invoke something more bizarre than Xenu is that they figured most Deltas would simply turn off the feature out of annoyance, and thus Microsoft would bear no blame in the subsequent (and likely rapid) zombification of said Delta's system.

      "What? We put the thingy in. It's not our fault if idiotsticks turns it off because he's too lazy to take security seriously."

      This is a way to let themselves off the hook, escalating user error to the root of all evil instead of, say, a hopelessly fractured and bloated development bureaucracy overseen by demented lizard people. This is a response to the criticisms about Windows having a default configuration more favourable to trojans than users, so they can now claim that the default configuration is solid. You changed a setting? The buck stops at you, sucker.

      Maybe Microsoft needs someone with some insight into user behaviour and interface psychology on staff. I hear Steve Jobs has a reasonable hourly rate. (/me ducks)

      • by an.echte.trilingue (1063180) on Tuesday February 13 2007, @04:43PM (#18003698) Homepage
        You know what really gets me about the annoying Vista security model? It's that the one in XP isn't THAT bad, its just the default configuration that is THAT bad. If you (1) password protect the "administrator" account and (2) run as a non-admin user when not doing admin things (most of the time), you will eliminate many problems.

        I know, I know, it is still not as good as *nix security, and there are lots of programs that need admin privileges to run properly (fewer these days, though), but it isn't that bad.

        Take care

        -mat

        • by AeroIllini (726211) <aeroillini&gmail,com> on Tuesday February 13 2007, @07:01PM (#18005540)

          I know, I know, it is still not as good as *nix security, and there are lots of programs that need admin privileges to run properly (fewer these days, though), but it isn't that bad.

          You know, if any *nix software required the user to be root to run, we would string the developers up alongside the guy who thought Clippy would be a good idea.

          Why should it be any different for third-party applications requiring Administrator privileges to run on Windows?

          Microsoft is so busy catering to the third party developers in order to maintain their lock-in, that they forgot how to put their foot down on truly important software engineering issues, like security. Locking down XP to an almost *nix-like state can be done. There are read/write/execute permissions available on every directory, drive letter, and registry key, and Windows supports the "home directory sandbox" model. After all, a virus in *nix could conceivably blow away a user directory, but unless it's exploiting a buffer overflow or other coding error hole, it can't take down the system. The same is possible in Windows, but not available by default to your average Dell user.
    • by tiltowait (306189) on Tuesday February 13 2007, @04:16PM (#18003232) Homepage Journal
      Video version of the above commentary here [apple.com].
    • by nuzak (959558) on Tuesday February 13 2007, @04:17PM (#18003242) Journal
      You want to run an application, is that okay? You want to copy a file, is that okay? You want to change your desktop background, is that okay? You want to copy text from IE7, is that okay? You want to turn your machine into a child porn and warez server, is that okay? You want to delete an old text file, is that okay? You want to paste text into a form field in IE7, is that okay?

      One of these things is not like the others,
      One of these things just doesn't belong,
      Can you tell which thing is not like the others
      By the time I finish my song?
    • by giafly (926567) on Tuesday February 13 2007, @04:35PM (#18003550)
      The truth is out. Microsoft didn't kill clippy [cnn.com] in MS Office, they just moved him upstairs to an entire operating system designed to ask unwieldy and confusing [eweek.com] questions.

      This link allegedly tells you how to turn the questions off [microsoft.com], but unfortunately I can understand the words, even most of the sentences, but the whole thing is just dreadful, "As a result, IT departments often cannot gauge the holistic health and security of their environments." Can anyone help?
    • by EXMSFT (935404) on Tuesday February 13 2007, @04:39PM (#18003612)
      UAC is so amazingly, fundamentally flawed. Has been from the beginning. As you noted, it's susceptible to user numbness. It's also susceptible to the dancing pigs phenomenon, something mentioned by Microsoft's own Steve Riley (see http://www.microsoft.com/technet/community/columns /secmgmt/sm0405.mspx [microsoft.com], and search for the words "dancing pigs".

      Mac has issued a salutation. Allow or deny? Comedy gold, and yet Apple hit the nail on the head.

      My expectation is that at least 50% of Windows Vista consumers will turn UAC off entirely, and the remaining 50% will ignore it (psychologically disable it) to the point that it may as well be disabled - especially applies in the enterprise computing world where Joe won't be allowed to turn it off, but still wants to do whatever he wants. Meaning that in the default configuration of users as hobbled admins, every Vista user is then an admin. Just like they are in XP. Really validates 5 years of hard work on security.
    • NTFS partitions NOT created by Vista will cause these prompts for file operations on them, because you do not have access to them. #1: Your XP user account does but it is not recognized by Vista. #2: Administrators permissions is only granted after a UAC prompt. #3: Users permissions are normally low. Hence the need to prompt you to get the proper permissions.

      Fortunately this is easy to fix. Simply go into the security settings in the property pages of a folder (or the whole drive if you wish) and add your personal account to the access list with full control. This will eliminate the prompts. Alternately on a multi-user computer you can adjust the permissions of the Users group for the same effect.

    • Apple got it right (Score:5, Insightful)

      by ruiner13 (527499) on Tuesday February 13 2007, @04:49PM (#18003784) Homepage
      There are 2 ways to install software.

      1. Drag application folder where ever you want it
      2. If application does need to install a control panel, kext, or any other system file, then you can create an installer. When the installer tries to install the files that need the elevated permissions, it then tells you what it is trying to do and asks for an admin user/password

      How is that hard to grasp at MS? Assuming everything needs admin permissions is just insane, and insisting it isn't a security hole and is a "design choice" is just fucking retarded.
        • by ruiner13 (527499) on Tuesday February 13 2007, @05:08PM (#18004054) Homepage
          No, it is completely different. For an MSI to run on windows, it needs to use the installer SERVICE which is running under the sytem account. This means that any installer inherently is running through a system user account. And if you had read the article, EVERY installer asks to be run as administrator in Vista, regardless of its intent. There is no exception made for a game, such as Tetris. RTFA yourself.
      • by KingSkippus (799657) * on Tuesday February 13 2007, @04:18PM (#18003268) Homepage Journal

        That's the thing. Most of the prompts I was getting was not from software trying to do stuff, it was from normal operating system operations such as copying/moving/renaming/deleting files. Not OS files, but my own documents in my user directory. Not programmatically, but from me personally interacting with Explorer to manage my data. Stuff like changing the layout of my Start menu. Stuff like changing my desktop background. Stuff like copying a line of text from a web page in IE7 to paste in a document.

        • by 787style (816008) on Tuesday February 13 2007, @04:33PM (#18003516)
          I had probably the most frustrating ten minutes i have ever spent on a computer before.

          Start, typed in regedit enter.
          Vista:Are you sure you want to run this program?
          Me: Yes. I went OUT of my way, hit start, run and typed in the pogram name I wanted. Thanks for checking though. (click) ....
          Edit the registry, close it. That was easy. ....
          double clicked on setup. Stupid shield on my icon, what does that mean?
          Vista: are you sure you want to run this? it's a program, you know.
          Me: Oh that must be what the shield is for. Vista feels like it should protect me from software!
          Vista: This is from AMD. Do you trust AMD?
          Me: yes, they pay me. I trust them. (click) .....
          Install......that was easy. ....
          Oops, there's a problem. Well, let's grab the correct file from the build server and copy it over ...
          Open my computer, go to program files ....
          Vista: Are you sure you want to go there?
          Me:Yes (click) ...
          open up the application folder ....
          drag a file from a network share to the application folder....
          Vista: Are you sure you want to overwrite this file?
          Me: Yes (click)
          Vista:A program wants to write to the Program Files folder. Is this ok?
          Me: Yes (click)
          Vista:You are trying to copy from a network share to the program files folder. This isn't allowed. Hit ok.
          Me: (Pounds head) (click) ....
          Drag to Desktop. ....
          Drag from desktop to application folder. ...
          Vista:
          Are you sure you want to overwrite this file?
          me: for the love of god yes
          Vista:A program wants to write to the Program Files folder. Is this ok?
          Me: Die.Die.Die.Die.
          • by LiquidCoooled (634315) on Tuesday February 13 2007, @04:41PM (#18003648) Homepage Journal
            Sounds like Clippy has been re-incarnated.

            *shudder*
            • by Minwee (522556) <dcr@neverwhen.org> on Tuesday February 13 2007, @05:06PM (#18004020) Homepage

              He did warn us that if we struck him down he would become more powerful than ever.

              Maybe we should have listened.

            • by hackstraw (262471) * on Tuesday February 13 2007, @05:36PM (#18004468) Homepage
              Sounds like Clippy has been re-incarnated.

              The sad thing is that I've seen Clippy like once or twice years ago, and that is what I thought this dialog reminded me of, but worse because from what I remember Clippy would start yelling at you when you did anything, and you could just tell him to go away, but now its worse because the operating system blocks and asks you to click a bozo box every time you do anything?

              * smashes head on desk *

              Let me be clear, I don't use MS software because it is not designed for a computer professional like myself. To be honest, I don't know who its designed for, or if its even designed at all.

              The first time I heard Windows was having this UAC thing, I knew that it would suck as only Microsoft could make it suck. I knew it would annoy the hell out of the user so bad that it would do one of two things. 1) annoy them to the point that they just turn it off (I understand this is allowed in Vista) 2) annoy the user and they don't turn it off, they just bend over and take it, and the 1 out of a million clicks when your supposed to say No, you click Yes because that is what you ALWAYS HAVE TO DO TO GET ANYTHING DONE.

              * smashes head on desk again *

              Microsoft can't even rip off existing security models that work like the elevated priveledges in OS X. Microsoft embarasses me as a computer professional, and I don't even use their stuff, because people associate MS with computers.

              Thanks for the grandparent post for sharing their experience, and thank you Apple, Linux, and Sun for making computers usable.

              Oh, and I almost forgot.

              Vista automatically assumes that all setup programs (application installers) should be run with administrator privileges -- and gives the user no option to let them run without elevated privileges.

              Isn't this the case where 99.9% of the time YOU WANT TO BE ASKED? Didn't Microsoft invent the term "driveby install"?

              * smashes head on desk again *

              • by PhotoGuy (189467) on Tuesday February 13 2007, @07:16PM (#18005718) Homepage
                Microsoft embarasses me as a computer professional

                Wow, I had never heard anyone said it so succinctly, but that's it, baby. I always felt an unrecognized sense of shame for the state of computers today, and I never quite realized why. This is it. Things should be *soooo* much further along today, if it weren't for the predatory monopolistic effects of MS. Throughout so much of the short PC history, there were rays of sunshine (Quarterdeck's multitasking DOS thing, many IP stacks, etc., etc), that were quashed by their monopoly. To see this happen, and realize their mediocracy, and not have done anything about it, definitely brings a sense of shame.
                • by PopeRatzo (965947) * on Tuesday February 13 2007, @07:44PM (#18006008) Homepage Journal
                  My few hours with Vista taught me something important about operating system design. That is, a good operating system should make you feel like you're in control of your computer. Like you're the one calling the shots and that the system will do exactly what you want it to do without fuss. Further, the experience of using a good OS should make you TRUST your computer and feel as if your computer TRUSTS you. You should not have to beg an OS to install an app or run an executable. Even if you do something that is possibly dangerous to security, the most it should do is ask "are you SURE?"

                  I don't want to wonder if my computer is tattling on me if I'm downloading an mp3 without DRM or watching a copy of a video that a colleague gave me. I don't want to think my computer is a rat or a punk. I don't want to think my computer will rebel if I run a perfectly legal program like Alcohol or rip.net or want to install the k-lite mega codec pack.

                  DirectX10? It's going to take more than DirectX10 for me to accept my computer as a spy in my home.

          • by Paolo DF (849424) on Tuesday February 13 2007, @05:09PM (#18004064)
            So, this is *exactly* like the latest "get a Mac" ad. Maybe even funnier!
          • by be-fan (61476) on Tuesday February 13 2007, @05:17PM (#18004198)
            Most of those prompts were redundant, either because they enforce things guaranteed by the underlying file permissions, or because the authorization could've been cached.

            Vista:Are you sure you want to run this program?

            Of course! It's got +X set!

            Vista: are you sure you want to run this? it's a program, you know.

            Ditto.

            Vista: This is from AMD. Do you trust AMD?

            Redundant. If I didn't trust them, I wouldn't have set +X.

            Vista: Are you sure you want to go there?

            Since Program Files shouldn't be world writable, this should prompt you for the administrator password. This authoriation should then be cached for Explorer.exe.

            Vista: Are you sure you want to overwrite this file?

            I'll let this slide, because even 'cp' prompts for that.

            Vista:A program wants to write to the Program Files folder. Is this ok?

            Should've grabbed cached authorization for Explorer.exe. Unless Explorer.exe was compromised in the 30 seconds between this action and the previous one, no security is lost here.

            Vista:You are trying to copy from a network share to the program files folder. This isn't allowed. Hit ok.

            That's just idiotic.

            Are you sure you want to overwrite this file?

            Again, I'd let it slide depending on preference.

            Vista:A program wants to write to the Program Files folder. Is this ok?

            Cached authorization again.

            It's really not that hard. UNIX/sudo got this right god knows how long ago. Apple did the right thing and just copied the sudo mechanism wholesale. Microsoft should to.
            • by Durandal64 (658649) on Tuesday February 13 2007, @06:29PM (#18005166)
              At the command line, Apple simply uses sudo. At the GUI layer, the security architecture is more complex than sudo. It borrows some concepts, but only in a very limited sense. When you authenticate, you don't necessarily become root. Sometimes, you are just given permission to make modificaitons within a program, where root privileges aren't strictly required for anything, but the app's author wanted to restrict certain capabilities to admin users on the machine. Apple's security model is designed around requesting rights (like "com.apple.installer.installSoftware") from the security server, and those rights have certain properties that you can set, like a timeout, whether root privileges are actually required for this right, etc ... In many cases, you're authenticating for permission to run a SetUID command-line tool that's been factored out of the GUI app you're working in. For example, when you authenticate in Installer.app, Installer.app does not elevate to being run with root privileges. It launches a SetUID binary called "runner", which runs with as root.

              Apple copied sudo's idea of "least required privileges" as the basis of its GUI security model, but I don't know if sudo was the first example of LRP. Maybe it was. But the GUI security model is definitely more complex than sudo, and apparently, it's a hell of a lot better than what Microsoft came up with for Vista. Using heuristics to identify which executables should get admin rights just seems like a horrendously stupid idea. Microsoft should've put its foot down on this one and forced developers of installer applications to properly request credentials. But they chose backwards-compatibility, as always, and now they're basically guessing who needs admin rights and who doesn't.
              • by Chris Burke (6130) on Tuesday February 13 2007, @06:42PM (#18005326) Homepage
                cause then there will be a story on here going on about how Microsoft stole from Unix, then we get 800 comments about how microsoft is evil for doing it, yet no one will mention that Apple did the same thing cause they aren't the evil microsoft.

                Whatever. For starters, Apple didn't just steal from Unix, they build their OS on top of Unix. And you can't read any article on OSX around here without a dozen posts pointing that out, so the "no one will mention" part is just crap. Of course Apple never hid the fact that they were "stealing" Unix by building their OS on top of BSD. The whole point being to start with a solid OS with all these great Unixy concepts built in and add their Apply interface on top. Whereas when Microsoft steals these features after another five years, they'll act like they were struck by inspiration out of the blue and done something that nobody's done before, like they have with every other idea they've stolen. So the "did the same thing" part is crap too.

                It may be fun and easy to take a poke at the "/. doublestandard", but it only reveals that you don't understand that it isn't a double standard at all. Microsoft has a bad rep for a reason among those who have been paying attention, and hey, maybe you don't know or understand why but don't think Apple would get a pass if they truly did the same things Microsoft does.

                Next up: Why viewing Halliburton in a harsher light than Bob's General Contracting is also not an unfair double standard.
          • by shmlco (594907) on Tuesday February 13 2007, @05:20PM (#18004254) Homepage
            "You are coming to a sad realization. Cancel or Allow?"
          • by bleifuss (821130) on Tuesday February 13 2007, @05:28PM (#18004366)
            You were lucky. Try logging into Vista using a domain account. Then try copying a file from a restricted share to which the local machine users are not automatically authenticated but to which the logged in domain user is. Try to copy the file to a restricted destination like C:\. You go to do the copy, get all of the prompts you listed and then guess what: when you authenticated to the remote share by logging into the machine you authenticated as the domain user, but the local administrator under whose context the elevated copy is being performed never authenticated to the remote share and you get prompted yet again for credentials.

            This is an annoyance for an end user but a major pain in the neck for software. I develop software that does not run elevated that accesses a remote file and the passes the file path into an out-of-process server that is running elevated. We either had to make the server no longer run elevated or prompt the user for credentials they already used to log into the machine (and which they don't think they need because they can get to the files just fine themselves) and then pass these credentials to the server with the path. Fortunately our architecture allowed us to have our server to not run elevated and get some other server to do the tasks that needed to be done elevated.

            Vista is really a pain in the neck. What's funny about it is that I was at a Vista iterop event at Microsoft last November (yes I sometimes have to fraternize with the enemy) and every MS developer I worked with had to tell me how much they loved working on Vista and that they had been using Vista on their development machines for months. I asked them if they had disabled UAC and they said "no, why would you want to do that?" I then asked them if it wasn't annoying to be prompted all the time and they said "no." I can only assume that they must have been brainwashed.
                • by Rycross (836649) on Tuesday February 13 2007, @05:15PM (#18004158)
                  Its mostly because Windows has been so piss-poor with their default settings in the past, so trying to get a more secure-by-default setup is like pulling teeth. I remember once reading in a security book that integrating security into your application after the fact is several times harder than designing it that way by default. Windows is in the unenviable position of having to integrate security after the fact.

                  Regardless, I think that a Windows version of sudo is a very good step. They just should have spent more time working on permissions so that it didn't trigger so much (assuming that what the posters' have said is accurate). The setup thing in TFA is kinda stupid, but installers almost always write to Program Files in Windows, and rarely have a per-user installation method like in Linux. A better solution would have been to try and encourage installers to have a per-user installation method.

                  Anyways, it may be that I'm just lucky that I haven't had a lot of problems with UAC. But I haven't had to go registry diving or modify any system directories in Vista yet, so theres that too.
                • by Bastard of Subhumani (827601) on Tuesday February 13 2007, @05:36PM (#18004464) Journal
                  Classic windows security. You can either do anything, or you can't even change the background picture.
            • by pherthyl (445706) on Tuesday February 13 2007, @06:19PM (#18005030)
              People bitch when it's so easy to get this stuff on a windows machine, Microsoft finally does something about it and people decide to bitch about that.

              No, people aren't bitching about them doing something, they're bitching about them doing something WRONG. Linux and Mac's have a similar approach to this problem, but their solution (sudo) is not annoying, so it actually works. All Microsoft had to do was copy that solution to improve security, instead they came up with their own and made it obtrusive in the process.

              I have yet to experience these supposed headaches with Vista yet, the only time that shield pops up is when I run a program that is potentially harmful to my computer

              Although I also have not seen these prompts when copying text, I have seen them in plenty of places aside from installing programs. Places that make absolutely no sense, such as storing wireless settings. There is no reason that action should require admin privileges and thus a prompt.

              How many story's were posted about programs looking like they came from an official place only to release a trojan? sure you get a program from download.com and figure it's safe but after installing a program it suddenly fucks up your PC, with Vista it will actually ask if you trust it let you know where it came from the works.

              And how would that help? You download a program from somewhere, and double click to install it. Whether it is a trojan or not, Windows is going to ask you for permission. Since you downloaded it, you obviously think it is not a trojan, so you would press Ok on the permissions dialog. Turns out it is a trojan, and your system is compromised. A permission dialog does nothing to protect you here.
            • by Stamen (745223) on Tuesday February 13 2007, @06:34PM (#18005212)
              What you aren't understanding is: it isn't the concept of asking for permission when you need to do something that requires administrator rights, that Microsoft got right, it's the way they implemented this feature that is so bad. Microsoft often gets the general ideas right, but the details are so wrong.

              Higher up in the thread someone mentions what happens when you copy a file to a folder in Program Files. Because Program Files folders are protected you need elevated permissions to do that. The right thing to do is say that it requires elevated permissions, ask if you want to do it, then do it. But in some cases it asks you 3 times for one file (do you want to copy, do you want to elevate, do you want to overwrite, do you want to be admin, do you need help with writing your letter). Why can't they give you one box that says, "The file already exists and this copy requires administrator rights, do you want to allow this?", then when you say OK, you are done. Why, why, why can't they do this, are they short of money?

              And Mac and Linux do exactly the same thing, they ask your permission to do admin tasks, except they got the details right so they don't irritate the user to death. A guarantee people are just going to shut off UAC because it's annoying, defeating the whole purpose.

        • by ThinkFr33ly (902481) on Tuesday February 13 2007, @04:43PM (#18003690)

          Not OS files, but my own documents in my user directory.
          I find that hard to believe, unless you're talking about pre-RC2 Vista. Operations on files which you own or have normal permissions to, such as all the files in your user directory, do *not* cause a UAC prompt. Simple as that. Think of it this way, if you were on Unix, it would simply deny you access to the file in question. You would then have to su root to get the job done. In Vista, it makes that elevation a lot faster and easier.

          For repeated, but seperate operations (like installing a lot of applications when you're setting up your machine), you can disable UAC. This is basically the same thing as su root if your account is an admin account. Once you're done, re-enable it. It's really not that hard.

          Stuff like changing the layout of my Start menu.
          You'll only get a UAC prompt when modify start menu folders that are shown to all users. Why? Because these aren't folders you own. See my previous point. Also, why bother rearranging start menu folders in Vista? If you want to find something, type in the first couple of letters and it appears. It's MUCH faster than drilling down through folders.

          Stuff like changing my desktop background. Stuff like copying a line of text from a web page in IE7 to paste in a document.
          You're either making this up, or you were using something that was even pre-pre RC1. This simply does not happen with Vista post-RC1.
      • by ucblockhead (63650) on Tuesday February 13 2007, @04:59PM (#18003918) Homepage Journal
        I'm a Windows developer. Last time I got a new machine, I counted the number of applications that I needed to install to completely set up my development environment. That number was over forty. You're telling me that I need to track changes to every one of those applications? Not easy on an OS that doesn't have anything like apt...one reason that while I write Windows code by day I run Linux at home.

        There have also been a number of times in my career where I have had to use development software written by companies that either went out of business, or stopped supporting that software. What then?

        What Apple understands and Microsoft does not is that it is not my job to make the OS work better. It is the OS's job to make my life easier.
        • by Chokolad (35911) on Tuesday February 13 2007, @05:01PM (#18003942)
          I still don't understand where the supposed security gain is. Since when is malware unable to click ok itself?

          UAC prompt opens in separate logical desktop. Applications from main desktop can not send windows messages to it which means malware will be unable to click ok itself.
          • by RzUpAnmsCwrds (262647) on Tuesday February 13 2007, @06:49PM (#18005404)

            You ARE prompted when doing something that will affect other users of the system


            You mean like modifying files that you don't have ownership of?

            UAC does not, and has never, prompted users when they move files that they have permissions to. It does, however, prompt when you move files that are in the common desktop or in the common start menu folders.

            Of course, linux and OSX have fine-grained mechanisms to grant/revoke permissions for any file, folder, or program.


            Clearly, you don't understand anything about how Windows works. Windows has had access control lists practically everywhere in the OS since Windows NT.

            Oh, and the ACLs in Windows are far, far more "fine-grained" than the usable-but-primitive permission bits in Linux.

  • by Lethyos (408045) on Tuesday February 13 2007, @04:11PM (#18003118) Journal

    Why not just let the user copy the application bundle to wherever they have write permissions? That application then executes with the privileges of the user that invokes it. If only there was a platform that offered such a simple an effective solution.

        • Re:Another approach. (Score:5, Informative)

          by TheRaven64 (641858) on Tuesday February 13 2007, @04:59PM (#18003926) Homepage Journal
          Actually, the concept was on the original Mac before NeXT existed. Mac applications would have the executable in the data fork, and any supporting 'files' in the resource fork. NeXT didn't want to implement forks, so they used folders instead. This let them store applications on filesystems that didn't support forks (e.g. FAT, UFS, etc), and so was probably a better solution.
  • Further proof (Score:5, Insightful)

    by Anonymous Coward on Tuesday February 13 2007, @04:15PM (#18003214)
    ...that security needs to be designed in from the start to be effective, not a bolted-on afterthought.

    When are they finally gonna give up this retarded backward-compatibility-at-all-costs mindset and *really* rewrite Windows from the ground up? Microsoft owns Virtual PC for Christ's sake, so it's not like they couldn't include a sandboxed "classic" Windows for app compatibility for a few years.

    The one thing Apple did that Microsoft really ought to copy, they don't. Figures.
  • What? (Score:5, Interesting)

    by jamesshuang (598784) on Tuesday February 13 2007, @04:16PM (#18003234) Homepage
    So let me get this straight... deleting a shortcut [flickr.com] brings up a pile of popups, but installing something doesn't?! Who's trading security for annoyance here?
  • by ThatsNotFunny (775189) on Tuesday February 13 2007, @04:16PM (#18003238) Homepage
    Looks like "Ease of Use" is the morbidly obese 10-year-old kid on this see-saw, and "Security" is up in the air with her legs dangling, and all the kids are lookin' up her skirt.
  • by MarkGriz (520778) on Tuesday February 13 2007, @04:18PM (#18003266)
    Wasn't it the failure of the UAC that allowed the demons from hell to infiltrate Earth?

    I guess MS didn't learn anything from id.

  • Troubling ... (Score:5, Interesting)

    by eck011219 (851729) on Tuesday February 13 2007, @04:29PM (#18003456)
    ... particularly because Vista was supposed to address some of the problems Microsoft had when trying to balance security and ease of use in XP. We now live in a very dangerous time as far as digital stuff is concerned, and I think continuing to hide as much security from people as possible (while paying lip service to it in other ways like UAC) is foolish. End users are going to have to learn to be careful, and learn a little bit about security. Cars didn't used to have locks, either. Times change, and people have to adapt to it to some extent.

    That said, I personally very much liked the Vista user experience (I'm back to XP for now, but I had the beta and RC1). But after the first couple of days, I turned off UAC (and besides, I like to manage my security myself). It did nothing but ask me if I wanted to do what I was doing. Like another early poster here, I almost immediately reverted to clicking any damn OK button I saw. And God knows, I turned the sound off almost immediately. Moreover, I turned it off because it seemed like a talented Bad Guy would simply bury his Evil Code in something that seemed benign, and Joe User would just click through it. But all of that has been covered at great length in these hallowed halls already.

    My point is still this: the bad guys are out there now. That's just reality. Telling people not to worry and to go back to sleep doesn't serve anyone anymore. I don't think power user knowledge is necessary for the average person, but frank awareness of basic online safety puts it in the hands of the individual user to some extent, and eases some of the strain for the OS designers/engineers. Because while MS has made some dumb and dangerous mistakes in the past, I still think of it this way: when you're designing any piece of software, you can't completely anticipate the security issues that will come up a year down the road, and you can't reduce how hard a user will work to circumvent your attempts to protect them, no matter how inobtrusive they may be.

    I'm not defending MS for its past mistakes, oversights, poor execution, and so on, but I do think people need to pony up a little more energy to protect themselves. I'm no security expert, but it just seems like responsible living to me.
  • by RzUpAnmsCwrds (262647) on Tuesday February 13 2007, @05:32PM (#18004416)
    Everyone who complains that UAC is annoying doesn't understand that the purpose of UAC is to be annoying. UAC makes elevation a pain, in the hope that software creators will write software which doesn't need to elevate!

    VMWare 6, for example, constantly elevates on Vista. What do you want to bet that VMWare 7 won't?

    Well behaved programs elevate only when and where they have to. Even if 50% of Vista users turn UAC off, that's still 50% of your client base who is being constantly bombarded by elevation dialogs. The solution? Write your software so it doesn't need to elevate.

    As for the article - installers pretty much have to elevate. This is true on Windows and with Linux packages (when was the last time you ran apt-get without using sudo or running as root?). Some have pointed out that you can install most packages in Linux to be specific to your user account, using special flags. This, of course, is possible in Vista as well, if MSI packages are used.

    Note that I do agree that it's a problem that you can't override UAC detection. There needs to be a "don't run as administrator" option.
    • Re:So what's new? (Score:5, Informative)

      by DoofusOfDeath (636671) on Tuesday February 13 2007, @04:15PM (#18003220)

      I believe that even RPM on linux runs the install scripts with admin access...

      Yes, but at least in the RPM case, a regular unprivileged user cannot cause an untrusted program to run with kernel-level permissions. In Linux, that user would have to enter a privileged password (for sudo or root login). On Vista, a regular user who has no admin rights can choose to execute an installer program with kernel privileges.
    • Let's say rather that you need root authority to install rpm packages for use by all users.

      rpm itself doesn't require root authority, and if everything you intend to do with rpm happens in directories to which you have write authority, rpm will work just fine.

      By default, rpm does use directories (notably, in /var) which will require running with root authority; but this can be overridden with command line switches (say, to install an rpm which will only be used by you).

      RTFM.