Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 1011961" data-attributes="member: 32260">Using Aaron Locker is not more complicated than using OSA, because one has to run only one script (Create-Policies.ps1). The problem is of another kind - the AaronLocker policies can be useful at home mostly with a semi-static setup.I am not convinced that creating a dedicated application for HomeAppLocker (like H_C or SWH) is worth my time, because of the possible development of Smart App Control. But I do not exclude such a possibility in the future. For now, I am thinking about a simple loader that could work as follows:<ol>
<li data-xf-list-type="ol">All needed files are copied into the folder Windows\HomeApplocker.</li>
<li data-xf-list-type="ol">The 3rd party explorer is executed with system privileges.</li>
<li data-xf-list-type="ol">The PowerShell execution policy is temporarily changed to Remotely signed (and set to the previous setting after closing the loader).</li>
<li data-xf-list-type="ol">The content of Windows\HomeApplocker is displayed in the file explorer.</li>
</ol>[ATTACH=full]270826[/ATTACH]Now the user can use the file explorer right-click context menu and choose &quot;Run with PowerShell&quot; to create/display/delete policies. So, using HomeApplocker can be very easy.</blockquote>

[QUOTE="Andy Ful, post: 1011961, member: 32260"] Using Aaron Locker is not more complicated than using OSA, because one has to run only one script (Create-Policies.ps1). The problem is of another kind - the AaronLocker policies can be useful at home mostly with a semi-static setup. I am not convinced that creating a dedicated application for HomeAppLocker (like H_C or SWH) is worth my time, because of the possible development of Smart App Control. But I do not exclude such a possibility in the future. For now, I am thinking about a simple loader that could work as follows: [LIST=1] [*]All needed files are copied into the folder Windows\HomeApplocker. [*]The 3rd party explorer is executed with system privileges. [*]The PowerShell execution policy is temporarily changed to Remotely signed (and set to the previous setting after closing the loader). [*]The content of Windows\HomeApplocker is displayed in the file explorer. [/LIST] [ATTACH type="full" alt="1668989387630.png"]270826[/ATTACH] Now the user can use the file explorer right-click context menu and choose "Run with PowerShell" to create/display/delete policies. So, using HomeApplocker can be very easy. [/QUOTE]

Verification