![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Security and Windows Vista A forum for discussion on security issues with Windows Vista. (microsoft.public.windows.vista.security) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Hello:
Scenario: 1) Launch notepad.exe with High MIC label, create file, close file. 2) Launch notepad.exe with Medium MIC label, edit that same file, save the changes successfully. Isn't this a violation of the purpose of mandatory integrity control? A process with a lower label (Medium) is successfully editing a file created and saved by another process with a higher label (High)? I'm not certain, but I swear this wasn't possible with earlier builds of Vista... :-\ Any insight will be greatly appreciated! Thanks! |
|
|||
|
Hello,
I may be wrong on this, but I think the object integrity value is controlled thru the object permissions heirarchy. When a process is running, it can only write to objects/containers that have an equal or lesser integrity value than what it is assigned, but when it creates an object I believe that object inherits the MIC value from the container, unless explicitly set. This would explain the behavior in your example, as the file you created most likely would have been set to the NORMAL integrity value, which is writable from both admin and non-admin processes. -- - JB Windows Vista Support Faq http://www.jimmah.com/vista/ |