Enter your username and password.
Tip your editors:
Editorial Director:
Brian Lam | | Twitter
Editor:
Jason Chen
| AIM | Twitter
Features Editor:
Wilson Rothman
| Twitter
Senior Contributing Editors:
Jesus Diaz
| AIM | Twitter
Mark Wilson, Reviews
| AIM | Twitter
Contributing Editors:
Matt Buchanan
| AIM | Twitter
Adam Frucci
| Twitter
Sean Fallon
| Twitter
Jack Loftus
| Twitter
John Herrman
| Twitter
Dan Nosowitz
Chris Mascari
Kat Hannaford
| Twitter
Rosa Golijan
| Twitter
Chris Jacob
Columnist:
Brendan I. Koerner
Interns:
Don Nguyen
Kyle VanHemert
Comment Account Questions:
Please enter your email address to have your password reset.
Registering will give you a user profile and the ability to add other users as friends. To become a commenter, however, you need to audition.
Want to know more? Consult the Comment FAQ and legal terms.
You don't need to login to comment. Just enter your email address below.
See how your address will be displayed in the Comment FAQ.
02/06/09
And what does "next release" mean? I recall a vague statement at this here Gizmodo that this beta would be the last beta/RC release to the public.
02/06/09
02/04/09
02/04/09
02/04/09
02/04/09
But I'd like to see a Vista and 7 system get hacked side by side to see how much faster 7 really is to break into with UAC turned off.
02/04/09
02/04/09
02/04/09
Then they complain about it not doing it's job.
Come on, you can't have your cake and eat it too lol
02/04/09
01/30/09
01/30/09
Is there any scenario where Microsoft won't get blamed?
01/30/09
01/30/09
01/30/09
01/30/09
01/30/09
01/30/09
Linux has one of the most secure privilege systems, and only needs to prompt you for installing programs in root directories, or doing system-wide changes (like hardware level changes). The reason is the system is layered in a way that a user can change a lot without affecting others.
MS chooses to make everyone run in an admin-like level and just ask for each step. The more logical and easier way is to separate the things people NEED to change, not bug them when the HAVE to change them.
01/30/09
They didn't count on the programmers to say "how about we be lazy and blame MS for the problem".
01/30/09
The major UAC change that I think will make most people happy is the ability to disable the UAC prompt for certain actions or programs. Windows 7 moved more towards this, but it's not there yet. The user should only have to confirm something once and have the ability to make that the last confirmation. For example, in Vista, a program installed 2 files in the root of the drive. They were simple log files. To erase them, I had to confirm my actions via Windows dialogs and the UAC a total of 8 times. EIGHT confirmations to delete 2 non-MS log files?
UAC is a good idea, but it's not done right. Vista's UAC was a complete disaster. Windows 7's UAC seems to be huge improvement, but it can still do more to create a secure system without annoying the users as much.
01/30/09
MS originally released a 'Best Practices' that, had it been adhered to, would have made the changes you mention not necessary. It was easier to only program assuming everyone had admin rights, thus the concept of the 'lazy' programmers as they choose, for whatever reason, to ignore these best practices. It wasn't the application developers who got slammed as a result of this, it was MS, so now they are enforcing the policy, thus companies like Symantec, who did horrible little kluges with their crappy and invasive code screamed how unfair it was (the sad part here is they basically called out their own dev's as incapable), thus MS was forced to reduce security in the name of shoddy programmers everywhere.
01/30/09
01/30/09
01/30/09
Don't get me wrong, UAC, along with ACHI disk handling, is pretty much my only complaint about Win7Beta, which is awesome. Just, how the hell it can be so hard to implement as nicely as it's done on OS X?
01/30/09
01/30/09
It would be nice to be able to flag executables that I deem safe and don't want to be nagged about.
The Start menu issue seems to raise when trying to move links that are available for all users.
01/30/09
Try the following. Reinstall but when running the installer, right-click and run the installer as admin. After it installs, go to the shortcut, right-click "properties" and under the security tab, check "Run as administrator".
It's a bit of overkill but give it a try.
01/30/09
01/30/09
Your first step should usually be to change the properties to "Run As Administrator", which solves a lot of problems. Citrix would bug me until I did that. Seems like an extra step but I can understand why Microsoft doesn't want everyone to always run everything as administrator by default all the time.
01/30/09
As for the start menu. How often do u reorganize your start menu and what are you doing to run into privelge errors???
01/30/09
Microsoft, like Apple, has learned the value of ripping off Quicksilver.
01/30/09
Unless I'm missing something, the script would change the settings without you knowing. What you personally have it set to wouldn't make the slightest difference. If you were really paranoid you should check your UAC before every time you shut down and immediately after logging in.
01/30/09
01/30/09
You're probably in a cave wearing a tinfoil hat, or at least using Linux with all the redundant firewalls, antiviri, and total disk encryption on.
Sounds like my computer :P
01/30/09
01/30/09
sudo -u DeusExMach userdel LegoAddict
woot