ASP.net impersonation security
From: spo via DotNetMonster.com (forum_at_nospam.DotNetMonster.com)
Date: 05/16/05
- Next message: Kylin: "Meaning ?-----------------> ".ASPXAUTH""
- Previous message: Joe Kaplan \(MVP - ADSI\): "Re: DirectoryEntry.Invoke access is denied"
- Next in thread: Ravichandran J.V.: "RE: ASP.net impersonation security"
- Reply: Ravichandran J.V.: "RE: ASP.net impersonation security"
- Reply: Ken Schaefer: "Re: ASP.net impersonation security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 16 May 2005 17:24:39 GMT
Does .net impersonation have any security risks from the ntfs side of
things? We currently have our intranet apps placed on the webserver
uncompiled and I have a concern that a user can get to the code behind
pages. Is this a valid concern? Please let me know of any other security
issues you have come across in relation to impersonation, I need to prepare
an arguement for or against its use.
Thanks in advance,
~spo
- Next message: Kylin: "Meaning ?-----------------> ".ASPXAUTH""
- Previous message: Joe Kaplan \(MVP - ADSI\): "Re: DirectoryEntry.Invoke access is denied"
- Next in thread: Ravichandran J.V.: "RE: ASP.net impersonation security"
- Reply: Ravichandran J.V.: "RE: ASP.net impersonation security"
- Reply: Ken Schaefer: "Re: ASP.net impersonation security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]