![]() ![]() This option prevents downloads of executables under IE. ![]() Use Chromium because it is a non-signed programĬhromium comes as as win-zip file, just extract it to Program Files and no Medium rights programs can change it (Chrome itself neither) and because Chromium is unsigned therefore it will never get Admin rights (elevate to HIGH integrity level)Īdded 1806 trick to registry. To compensate for this protection, I allow only signed programs to elevate (Deny Elevation of unsigned) and hardened UAC (no installer detection, also build in admin under UAC). I have set UAC to automatically elevate (no prompt). Because, even if for a brief second Chromium's children processes may inherit a medium level and then go back to low integrity level, it must be fixed (if it's what's happening!). Perhaps, you could still try to code something that could reveal the real ILs? Who knows what's truly happening. Anyway, this quest did reveal something - don't fully trust anything, do your own findings. Hopefully, that's all it is - a glitch in Process Explorer, that for some reason cannot show the real ILs for Chromium/Chrome children processes, and an awkward way of Google developers have towards people seeking for answers.īut, all the ingredients did seem to point to a bug. By right-click that process and checking its Properties > Security, you'll see it's assigned a low integrity level. I find it confusing that Process Explorer has no problems of what so ever with IE8/IE9 and Adobe Reader X.Ĭould it also be that, for brief seconds, chrome.exe children processes may, in fact, inherit a medium integrity level, and then go back to a low integrity level? Hence the reason, when reopening Process Explorer, everything returns to normality?Ĭlosing and reoping Chromium, and then openening and closing tabs will result in Process Explorer show some of the children processes with a medium level. Nonetheless, I'll be waiting for what Google developers have to say. Now, I don't know if this means anything or not.īut, what started to raise my suspicion at Google's way of handling this, was telling to Kees1958 that it was a problem with Process Explorer, but not replying when he asked for some other tool he could use, or even to suggest to close and reopen Process Explorer and see if there would be any difference. I took note of the PIDs where chrome.exe (children) was assigned a medium level, and then I thought of something we never though of - Close and reopen Process Explorer.Īll chrome.exe processes (children) that were running with medium IL, according to Process Explorer, now run with a low integrity level. Click to expand.I tried a similar approach. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |