![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
|
Welcome to Vista Forums we are your forum to discuss Windows Vista x64 and x86 systems. Whether you need help or just want to post an idea you have on Vista, this is the forum for you.
br> br> |
| |||||||
![]() |
| | Thread Tools | Display Modes |
| | #1 (permalink) |
| Guest | Doesn't this example violate Mandatory Integrity Control? 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! |
| | #2 (permalink) |
| Guest | Re: Doesn't this example violate Mandatory Integrity Control? 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/ |
| | #3 (permalink) |
| Guest | Re: Doesn't this example violate Mandatory Integrity Control? 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/ |
| |
| |
![]() |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Re: Booting Vista from external drive violate MS EULA? | Mark Conrad | Vista General | 2 | 4 Days Ago 03:36 PM |
| RE: Booting Vista from external drive violate MS EULA? | Mick Murphy | Vista General | 2 | 2 Weeks Ago 08:22 AM |
| Code Integrity Errors | Blackjaw | System Security | 1 | 03-16-2008 10:43 AM |
| How to elevate integrity level of a process | Darshan Tilak | Vista security | 4 | 12-05-2007 03:43 AM |
| Mandatory Integrity Control (MIC) tools? Biba tools? | Sharon2323 | Vista security | 1 | 08-04-2006 01:13 PM |