Security Features and Memory Usage,...
in [Win32 Kernel]
|
Prev: Volume Shadow Copy Service error: Unexpected error calling routineCoCreateInstance. hr = 0x800401f0
Next: Opportunistic Background Processing On Idle Web Server
From: Paul Baker [MVP, Windows Desktop Experience] on 1 Mar 2010 08:15 You could post to a security newsgroup. This is a kernel newsgroup. As you know, security pervades the OS on many levels, not only the kernel. My *guess* would be that it's easily small enough that you could argue that security measures are more important than resource usage. You can easily upgrade memory, which negates the whole thing. Paul "Kerem G�mr�kc�" <kareem114(a)hotmail.com> wrote in message news:eyn6bT0tKHA.4568(a)TK2MSFTNGP05.phx.gbl... > Hi, > > thanks for the answers. I Know that my question sounds > a little strange and i am aware of the fact, that e.g. a > handle is not just a typedef to a new datatype and acls > are just some structs in memory and that there is so > much of more like describing headers, state information > and lots of internal memory and code handling and > maintaining this. My question was more like: If we strip > all the security stuff from the OS an expect everything to > run in one level/security,...ow much of code/memory > would we save. I just was wonderung how much of code/ > memory all this security features are covering on the OS > and when it runs how much of the OS memory does this > cover. I KNOW that this is a question that is hard or even nealry > cannot not to be answered, but i was wondering what others > can tell me about that,... > > Regards > > Kerem > > -- > ----------------------- > Beste Gr�sse / Best regards / Votre bien devoue > Kerem G�mr�kc� > ----------------------- |