Enter the world of win7 User Account Control (UAC)

  
                

I don't know if you've heard of User Account Control (UAC). This term originally appeared in the Vista system. It has always been the most watched, discussed, and controversial technology in the XP system. Now it's In the windows7 system, this function will be controversial for the win7 system? Or is it based on the award? This article will compare and analyze the new and old UAC technology to help you get the answer you want, Windows 7 user account control (UAC) Curious friends, come along with Xiaobian.

UAC design goals

The UAC function was originally designed to solve application problems that require administrative privileges. The end user is configured as a local administrator. In the beginning, UAC was called LUA (least privileged user access), but was immediately renamed because it was not just a solution to the problem.

The final product, UAC, is a security-related technology designed to protect operating system files and the registry from malware, viruses, and code attempts to update computer protected areas. The malware attempts to add, modify, and remove key components of the operating system to control the computer without being discovered.

UAC Runtime

(Vista and Windows 7) UAC works in a similar way. There are some features that Windows does not have in Windows 7, which we will discuss below. The job of UAC is to remove the "privilege" of the application, task, function or action performed by the user in the routine function. In fact, UAC is suitable for these two different modes: users who are members of the local administrators group and users who are not members of the local administrators group.

If you look at how the vista system's UAC function works, we can compare it to Windows 7. We need to look at these two modes of operation. First, let's look at the non-admin login, in which case the user does not have administrative credentials to log in, so that when the administrative privileges are required, all applications, any or features will Can not run. When the UAC function is enabled (a confirmation dialog will pop up by default), a dialog box will pop up for the user to enter the administrative rights account username and password. When entering this information, only the UAC function tag and the required application, task or function can have administrative rights to operate. The UAC popup confirmation dialog is displayed.

Next, we need to investigate the UAC of the Vista system in the "administrator" logged in, in this case, when the user logs in with administrator privileges, UAC will basically cancel all management Permissions, only until there are tasks that require administrative privileges. In doing so, background applications, viruses, malware, worms, etc. cannot use the login credentials to modify operating system files and the registry. If we look at the verification token after the user account that is a member of the domain administrators group is logged in, we can clearly see that "admin privilege" has been canceled. It is clear that the domain management group SID has set the token to “reject”.

This is the most important aspect of administrator login, because almost all malicious programs that are written use the current login information, and the malicious program can be invalidated when the token is rejected. Of course, the downside of this is that all applications (even those that are well known) will pop up a confirmation dialog at startup to start the program.

When you run a known application for the tenth time and see the confirmation box for the tenth time, you get bored. We know that safety has always been very troublesome. However, when doing so, when a malicious application tries to get close to a protected file or registry key, a prompt box appears prompting the user that something is running in the background, and the user has not started any programs.

This prompt for non-admins and administrators is UAC's safest mode, and any started task will require administrative privileges. Any protection mode that is lower than this cue mode does not protect the computer from malware or viruses, because background activity is hard to find and will change the system. Previous12Next page Total 2 pages

Copyright © Windows knowledge All Rights Reserved