Reply to thread

Message

<blockquote data-quote="Hi Brothers" data-source="post: 743497" data-attributes="member: 71794"><p>I want to have complete control over everything (I AM the process OVERLORD) so that&#039;s why I&#039;m not allowing anything by default. Like I said I&#039;m not sure that allowing child process chrome.exe being ran by parent process chrome.exe is 100% safe, because in that case any child process chrome.exe from parent process chrome.exe will be allowed, my goal is to have only specific child processes chrome.exe from parent process chrome.exe allowed (the ones that open for each tab), this way if there is another child process chrome.exe spawned from parent process chrome.exe that is different than what is needed for each tab, I&#039;ll be able to monitor it and make sure I need it before allowing it. If I do what you propose, I&#039;ll only have control of child processes chrome.exe being spawned from parent processes NOT chrome.exe, I want to have control over ALL child processes chrome.exe including those spawned by parent process chrome.exe, and whitelisting those spawned for each tab that&#039;s opened, which is currently impossible firstly because for each tab I have to whitelist the specific command line (of child process chrome.exe from parent process chrome.exe) all over again, and secondly because each time I close and reopen chrome the command lines are different so they won&#039;t be automatically allowed because the whitelisted commands from last time are with different numbers since the numbers change each time a new tab is opened or chrome is closed</p></blockquote><p></p>

[QUOTE="Hi Brothers, post: 743497, member: 71794"] I want to have complete control over everything (I AM the process OVERLORD) so that's why I'm not allowing anything by default. Like I said I'm not sure that allowing child process chrome.exe being ran by parent process chrome.exe is 100% safe, because in that case any child process chrome.exe from parent process chrome.exe will be allowed, my goal is to have only specific child processes chrome.exe from parent process chrome.exe allowed (the ones that open for each tab), this way if there is another child process chrome.exe spawned from parent process chrome.exe that is different than what is needed for each tab, I'll be able to monitor it and make sure I need it before allowing it. If I do what you propose, I'll only have control of child processes chrome.exe being spawned from parent processes NOT chrome.exe, I want to have control over ALL child processes chrome.exe including those spawned by parent process chrome.exe, and whitelisting those spawned for each tab that's opened, which is currently impossible firstly because for each tab I have to whitelist the specific command line (of child process chrome.exe from parent process chrome.exe) all over again, and secondly because each time I close and reopen chrome the command lines are different so they won't be automatically allowed because the whitelisted commands from last time are with different numbers since the numbers change each time a new tab is opened or chrome is closed [/QUOTE]

Verification