zekrahminator
McLovin
- Joined
- Jan 29, 2006
- Messages
- 9,066 (1.31/day)
- Location
- My house.
Processor | AMD Athlon 64 X2 4800+ Brisbane @ 2.8GHz (224x12.5, 1.425V) |
---|---|
Motherboard | Gigabyte sumthin-or-another, it's got an nForce 430 |
Cooling | Dual 120mm case fans front/rear, Arctic Cooling Freezer 64 Pro, Zalman VF-900 on GPU |
Memory | 2GB G.Skill DDR2 800 |
Video Card(s) | Sapphire X850XT @ 580/600 |
Storage | WD 160 GB SATA hard drive. |
Display(s) | Hanns G 19" widescreen, 5ms response time, 1440x900 |
Case | Thermaltake Soprano (black with side window). |
Audio Device(s) | Soundblaster Live! 24 bit (paired with X-530 speakers). |
Power Supply | ThermalTake 430W TR2 |
Software | XP Home SP2, can't wait for Vista SP1. |
When Microsoft shipped Windows Vista, they bragged about how secure it was, showing off the User Access Control (UAC) feature. UAC is something that asks a user if they really want it to run a program before simply running it (previous versions of Windows would simply run the program). "Hackette" Joanna Rutkowska found a disturbing loophole through UAC. Apparently, UAC works by running everything as an administrator, and simply asking for confirmation before executing a program. So if something like a game installer triggered off UAC, and a user hit "allow", the program could theoretically be allowed to run a bunch of other things that would individually require administrator privileges. When dealing with things like simple registry changes this is no problem, but when malware is piggybacking in an installer....this effectively ushers in the next generation of Trojan horse viruses. Microsoft does not consider this a serious threat, and thinks of it more like a minor weakness, which is the result of a "design choice".
View at TechPowerUp Main Site
View at TechPowerUp Main Site