SeDebugPrivilege

[RedLars]

Using WinXP Prof with IIS 5.1.

The computer is running a few web services (ASP.NET).

The problem, one of the services uses a dll which uses OpenProcess()
win32 api. This method needs SeDebugPrivilege to operate. For
debugging purposes I've used Process Explorer to check the security
level of processes (like aspnet_wp.exe).

In ...\v1.1.4322\CONFIG\machine.config the ASPNET service is
configured to username "machine" and password "Autogenerated".

Try adding Debugging privileges to ASPNET (Control Panel-

Adminstrative Tools->Computer Management) and rebooted computer. When

accessing the web service the aspnet_wp.exe does not have
SeDebugPrivileges (according to Process Explorer).

In ...\v1.1.4322\CONFIG\machine.config I change username to "System"
and password "Autogenerated" and reboot computer. When accessing the
web service the aspnet_wp.exe process has SeDebugPrivilege set to
"default enabled".

It seems odd that adding "debugging" privileges to ASPNET as no effect
on the users' privileges. Can anyone explain this? What am I missing?
Feel more comfortable using the ASPNET user.

 

[Evertjan.]

RedLars wrote on 01 mrt 2007 in microsoft.public.inetserver.asp.general:

The computer is running a few web services (ASP.NET).

This is a classic asp group.

Dotnet questions should be asked in
<microsoft.public.dotnet.framework.aspnet>

 

[RedLars]

Sorry for the incorrect posting.

Will re-post in group suggested.