Win2k3 Event Log and Security: Must choose between security and trustworthy
From: Craig Humphrey (Craig.Humphrey@nospam.chapmantripp.com)
Date: 04/24/03
- Next message: Nad Cyrus: "secure pdf files"
- Previous message: Mike Moore [MSFT]: "RE: UNC file share and NTLM user identity"
- In reply to: Jonathan Folland: "Win2k3 Event Log and Security: Must choose between security and trustworthy"
- Next in thread: andrew: "Re: Win2k3 Event Log and Security: Must choose between security and trustworthy"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Craig Humphrey" <Craig.Humphrey@nospam.chapmantripp.com> Date: Wed, 23 Apr 2003 18:18:45 -0700
Hmm... wouldn't it be easier to authenticate the login and
then impersonate the authenticated user? e.g. you could
log in as Administrator (heaven forbid) or a user with
Admin level privs (or at least privs to edit the event
log).
Failing that, you could wrap the code that works with the
event log with a specific impersonated user.
Have a look here:
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;306158
BTW MS seems to have gone out of it's way to discourage
people from impersonating the authenticated user. Don't
know why, on Intranets it's often vital and we happen to
use it (in plain ASP) on our Extranet services as well.
Just my 2c
Later'ish
Craig
>-----Original Message-----
>When developing ASP.Net apps in Win2k I encountered an
issue (many others
>have as well) regarding the way the EventLog.WriteEntry
encounters security
<snip snip>
- Next message: Nad Cyrus: "secure pdf files"
- Previous message: Mike Moore [MSFT]: "RE: UNC file share and NTLM user identity"
- In reply to: Jonathan Folland: "Win2k3 Event Log and Security: Must choose between security and trustworthy"
- Next in thread: andrew: "Re: Win2k3 Event Log and Security: Must choose between security and trustworthy"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
