UAC for Application Developers
page 1 of 5
Published: 29 May 2007
Abstract
In this article James examines what UAC is, how it works, why it is important and how to write .NET 2.0/3.0 applications that are compliant with it.
by James Bender
Feedback
Average Rating: 
Views (Total / Last 10 Days): 24405/ 45

Introduction

Over the past several years, the security of operating systems has become more and more important. In response to the perception that their operating systems are less secure than their Linux based competition, Microsoft has responded by integrating a new security mechanism called User Access Control (UAC) into their newest operating system Vista. In this article I will describe what UAC is and how it works, why it is important to developers, and how you can ensure that your .NET applications are compliant with the new paradigm.

UAC is designed to address the problem of malware. Most users, whether they need to or not, log in as local an Administrator. As a result, any application that runs in their session has full Administrator access to the operating system. This includes malware.

In short, UAC requires the user to confirm the execution of any application that requires elevated permissions. By doing this, malware is essentially cut-off from even being able to start. If you do not know the application that is asking for elevated permissions, simply do not allow it to execute.


View Entire Article

User Comments

No comments posted yet.

Product Spotlight
Product Spotlight 





Community Advice: ASP | SQL | XML | Regular Expressions | Windows


©Copyright 1998-2014 ASPAlliance.com  |  Page Processed at 10/31/2014 3:46:10 PM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search