news:1127826645.382804.14450@g43g2000cwa.googlegroups.com...
> Sorry I should also have said windows 2003 server as well.
>
> Kevin
>

> In addition to what Dominick said, under 2003, I suggest running each
> app in its own AppPool, setting the process identity to the identity
> you want to use and disabling impersonation via web.config.  Then, it
> is a non-issue.
>
> Joe K.
>
> <kevin.ke***@zygonia.net> wrote in message
> news:1127826645.382804.14450@g43g2000cwa.googlegroups.com...
>
>> Sorry I should also have said windows 2003 server as well.
>>
>> Kevin
>>

> Hi Guys,
>
> Thanks for replying. The problem I have is that this is a hosting
> platform that I've inherited. The servers can have up to 900 sites
> customer sites running on them. There is also no chance that the
> servers running Windows 2000 Server will be upgraded to Windows 2003
> in the near future.
>
> I did think about having an AppPool per site on 2003 but there are
> some practicality issues here and also I'm guessing that 900 AppPools
> isn't really the right answer from a scalability and management
> aspect.
>
> As far as the medium trust thing goes, unfortunately we have customers
> using OleDB in conjunction with Access database files.
>
> Is it possibile to build a custom trust level that has all the
> restrictions of Medium trust but allow OleDbClientPermission ?
>
> Can I create a new policy file based on 'medium_trust.config' and add
> the OleDbClientPermission? Is this good practice?
>
> Sorry if there are obvious answers to these questions but whilst I
> understand the concept and use of different trust levels, I'm a bit in
> the unsure about what to do regarding tuning the default policies to
> our needs.
>
> Thanks Again
> Kevin
> ps: Dominick, I enjoyed your sessions at DevWeek2005 this year.

> Hi All,
>
> Sorry to crosspost but it's a security and an ASP.NET problem I have.
>
> We run each website site under it's own I_<user> account and ASP.NET
> is configured to impersonate so requests run under the identity of the
> I_<user> account.
>
> In windows 2000 server how do I prevent a user from calling
> RevertToSelf() in advapi32.dll and unwinding the impersonation? e.g.
>
> [DllImport(@"C:\WINNT\system32\advapi32.dll")]
> public static extern bool RevertToSelf();
> void Page_Load(Object sender, EventArgs e) {
> // at this point the request is running under impersonation as
> I_<user>
> RevertToSelf();
> // afterwards it undoes the impersonation and the request is
> now running as <MACHINE>\ASPNET
> }
>
> I've looked into building a .NET security policy to do this but I'm a
> bit stuck.
>
> Thanks in advance.
> Kevin