Improve ASP. NET program Permissions

Source: http://blog.csdn.net/lake2/

Since Microsoft's. NET strategy began, many hosts have supported. NET. Here, I would like to say that 2003 supports. NET. To support. NET in 2000 and XP, I need to download. NET Framework from Microsoft (here is: aspx? FamilyID = 262d25e3-f589-4842-8157-034d1e7cf3a3 & displaylang = zh-cn "> http://www.microsoft.com/downloads/details.aspx? FamilyID = 262d25e3-f589-4842-8157-034d1e7cf3a3 & displaylang = zh-cn ). Well, now let's get started.

After. NET is supported, your IIS can run ASP. NET programs. In IIS5.x, ASP. NET program is run by an account named ASPNET belonging to the Users group. You can see it in the command line using net user. In IIS6, ASP. the NET program is run by the network service in the IIS_WPG group (IIS working process group). The net user account cannot be seen and can only be found in the IIS_WPG Group of the computer management account.

Ah, make an advertisement first. WebAdmin is an ASP independently developed by lake2. the Management Program in the. NET environment (or an excellent backdoor), but the permission is determined by whether to manage the web directory or the server. So, in order to keep a good post, we need to improve the permissions of ASP. NET programs.

It is quite simple to improve the permissions of ASP. NET programs. You only need to upgrade the account that executes ASP. NET programs to admin. 2003 is network service; 2000/XP is ASPNET. However, it may not be easy for you to obtain the admin permission-the Administrator will not use this software to manage the server. ^_^

Figure 1 shows the result of executing the at command in an ASP. NET program. Figure 2 shows the execution result after adding ASPNET to the admin group. Wait, I may find that some systems do not take effect immediately, so you have to wait patiently for the user permission.

Figure 1