Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve tried to add
System.Diagnostics.Debugger.Launch();
to my IIS ASP.NET web site code. I run the application as the standard AppPoolIdentity user and it pops up a debug window where I can choose to attach VS2010 and debug the process. My question is, what allows the AppPoolIdentity (virtual) user permission to interact with my desktop? Normally that’s not allowed. This was tested on Windows 7 x64.
Thanks!
When an unhandled exception occurs, there is a check done in the registry to see which debugger is listed.
32 bit systems use:
KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
This can also be the source of a security vulnerability – see
http://support.microsoft.com/kb/923827
for details on the AEDebug registry key see:
http://msdn.microsoft.com/en-us/library/5hs4b7a6.aspx
The app pool identity isn’t interacting with your desktop – the debugger request is. Nothing has ‘interacted’ until you choose to debug, at that time the debugger is launched and you attach to that process.