[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [DotGNU]Engine InternallCall
From: |
Rhys Weatherley |
Subject: |
Re: [DotGNU]Engine InternallCall |
Date: |
Fri, 11 Apr 2003 07:47:06 +1000 |
User-agent: |
KMail/1.4.3 |
On Wednesday 09 April 2003 02:16 am, address@hidden wrote:
> I'm interesting on this internalcall devel. Can you guys give me a guide
> about it?
>
> ILBool _IL_RuntimeSecurityManager_CanUseFileHandle(ILExecThread *_thread,
>
> ILObject *_this,
>
> ILNativeInt handle)
It was an aborted attempt on my part to implement a security policy. In the
.NET Framework SDK, it is possible to create a FileStream object based on a
raw operating system file handle that you have obtained via PInvoke. This is
quite insecure, so I added the internalcall as a placeholder for some future
"does the profile allow this" check.
It will probably be replaced with a CAS-based scheme instead once CAS been
fully implemented. (CAS = Code Access Security, or the stuff underneath the
System.Security.Permissions namespace). CAS is more flexible than adding a
check internalcall for every feature that is security-sensitive.
Cheers,
Rhys.