Reply to thread

Message

<blockquote data-quote="ForgottenSeer 97327" data-source="post: 1056081">These answers trigger questions, because you seem to evade direct answers:1. NO except except for whitelisted folders means YES it allows everything in whitelisted folders, correct?2. Do I understand you correctly that using Run by Smartscreen with WHH-version of WDAC and Run by Smartscreen using WDAC-ISG, the smartscreen works the same (trying to compare apples with apples)?3. Yes, I got a YES <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite130" alt="(y)" title="Thumbs up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" />___________About your comment on using Run By Smartscreen. I have three additional questions:4. How do you force to use &quot;Run By Smartscreen&quot;?5. I have read some posts about side loading using mising DLLs in the known DLL list which even Smartscreen missed. So I am unsure whether that Run By smartScreen is a fool proof solution for &#039;normal&#039; DLLs. How Does Smartscreen protecs&nbsp; from side loading DLL&#039;s when you exclude dotNet DLL&#039;s from WDAC blocking?6. In case of dropped DLL&#039;s, I fail to understand how run by smartscreen would protect the user when software updates from whitelisted folders using the dropped DLL&#039;s? That is the whole point of DLL side loading and hijacking, let regular (whitelisted) software run it?</blockquote>

[QUOTE="ForgottenSeer 97327, post: 1056081"] These answers trigger questions, because you seem to evade direct answers: 1. NO except except for whitelisted folders means YES it allows everything in whitelisted folders, correct? 2. Do I understand you correctly that using Run by Smartscreen with WHH-version of WDAC and Run by Smartscreen using WDAC-ISG, the smartscreen works the same (trying to compare apples with apples)? 3. Yes, I got a YES :) (y) ___________ About your comment on using Run By Smartscreen. I have three additional questions: 4. How do you force to use "Run By Smartscreen"? 5. I have read some posts about side loading using mising DLLs in the known DLL list which even Smartscreen missed. So I am unsure whether that Run By smartScreen is a fool proof solution for 'normal' DLLs. How Does Smartscreen protecs from side loading DLL's when you exclude dotNet DLL's from WDAC blocking? 6. In case of dropped DLL's, I fail to understand how run by smartscreen would protect the user when software updates from whitelisted folders using the dropped DLL's? That is the whole point of DLL side loading and hijacking, let regular (whitelisted) software run it? [/QUOTE]

Verification