Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Hard_Configurator Tools
Hard_Configurator - Windows Hardening Configurator
Message
<blockquote data-quote="wat0114" data-source="post: 969758" data-attributes="member: 91306"><p>I can relate to what Kees is getting at, because I remember being puzzled about this here:</p><p></p><p>[URL unfurl="true"]https://malwaretips.com/threads/hard_configurator-windows-hardening-configurator.66416/post-957044[/URL]</p><p></p><p>...and you responded soon after here:</p><p></p><p>[URL unfurl="true"]https://malwaretips.com/threads/hard_configurator-windows-hardening-configurator.66416/post-957068[/URL]</p><p></p><p>...and your explanation made sense to me then, and still does today. I used to block those types of user directories when I ran SRP alone without H_C, but then so many complex and granular rules are required that most people don't have the time nor patience to deal with, such as:</p><p></p><table style='width: 100%'><tr><td><p style="text-align: left">C:\Users\user\AppData\Local\PCHealthCheck\PCHealthCheck.exe</p> </td></tr><tr><td><p style="text-align: left">C:\Users\user\AppData\Local\Temp\*-*-*-*-*\dismhost.exe</p> </td></tr><tr><td><p style="text-align: left">C:\Users\user\AppData\Local\Temp\*-*-*-*\*.dll</p> </td></tr><tr><td><p style="text-align: left">C:\Users\user\AppData\Local\Temp\*.tmp\GoogleUpdate.exe</p> </td></tr><tr><td><p style="text-align: left">C:\Users\user\AppData\Local\Temp\*.tmp\System.dll</p> </td></tr><tr><td><p style="text-align: left">C:\Users\user\AppData\Local\Temp\n*.tmp\nsRandom.dll</p> </td></tr></table><p></p><p>...and of course as you explained, for the Home user these types of restrictions are not needed.</p></blockquote><p></p>
[QUOTE="wat0114, post: 969758, member: 91306"] I can relate to what Kees is getting at, because I remember being puzzled about this here: [URL unfurl="true"]https://malwaretips.com/threads/hard_configurator-windows-hardening-configurator.66416/post-957044[/URL] ...and you responded soon after here: [URL unfurl="true"]https://malwaretips.com/threads/hard_configurator-windows-hardening-configurator.66416/post-957068[/URL] ...and your explanation made sense to me then, and still does today. I used to block those types of user directories when I ran SRP alone without H_C, but then so many complex and granular rules are required that most people don't have the time nor patience to deal with, such as: [TABLE] [TR] [TD][LEFT]C:\Users\user\AppData\Local\PCHealthCheck\PCHealthCheck.exe[/LEFT][/TD] [/TR] [TR] [TD][LEFT]C:\Users\user\AppData\Local\Temp\*-*-*-*-*\dismhost.exe[/LEFT][/TD] [/TR] [TR] [TD][LEFT]C:\Users\user\AppData\Local\Temp\*-*-*-*\*.dll[/LEFT][/TD] [/TR] [TR] [TD][LEFT]C:\Users\user\AppData\Local\Temp\*.tmp\GoogleUpdate.exe[/LEFT][/TD] [/TR] [TR] [TD][LEFT]C:\Users\user\AppData\Local\Temp\*.tmp\System.dll[/LEFT][/TD] [/TR] [TR] [TD][LEFT]C:\Users\user\AppData\Local\Temp\n*.tmp\nsRandom.dll[/LEFT][/TD] [/TR] [/TABLE] ...and of course as you explained, for the Home user these types of restrictions are not needed. [/QUOTE]
Insert quotes…
Verification
Post reply
Top