Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 1062647" data-attributes="member: 32260">The Two Accounts Setup is kinda similar to the idea of Sandboxie or ReHIPS. The second account can be understood as the &quot;light sandbox&quot; which requires a password.Edit.There are some differences, though.The classic sandboxes have strong isolation and virtualization but allow running malware. So, the user can be spied on, except if the Internet connection is disabled in the sandbox. In theory, the malware can escape from the sandbox when a highly privileged exploit is applied, but I never heard about such malware in the wild - probably no one bothered to bypass Sandboxie or ReHIPS in that way.The WHHLight &#039;sandbox&#039; is a light sandbox. The isolation and &quot;virtualization&quot; is limited (in theory) to processes running with standard rights, but the user can run only safe files. In practice, WHHLight &quot;sandbox&quot; can prevent UAC bypasses, so the problem can arise only with rare (highly privileged) exploits.There are some other differences like the amount of folders shared with a &quot;non-sandboxed&quot; account (default Admin account), etc.But, from the viewpoint of the default Admin account, we have the isolation and virtualization expected when using a sandbox.</blockquote>

[QUOTE="Andy Ful, post: 1062647, member: 32260"] The Two Accounts Setup is kinda similar to the idea of Sandboxie or ReHIPS. The second account can be understood as the "light sandbox" which requires a password. Edit. There are some differences, though. The classic sandboxes have strong isolation and virtualization but allow running malware. So, the user can be spied on, except if the Internet connection is disabled in the sandbox. In theory, the malware can escape from the sandbox when a highly privileged exploit is applied, but I never heard about such malware in the wild - probably no one bothered to bypass Sandboxie or ReHIPS in that way. The WHHLight 'sandbox' is a light sandbox. The isolation and "virtualization" is limited (in theory) to processes running with standard rights, [B]but the user can run only safe files[/B]. In practice, WHHLight "sandbox" can prevent UAC bypasses, so the problem can arise only with rare (highly privileged) exploits. There are some other differences like the amount of folders shared with a "non-sandboxed" account (default Admin account), etc. But, from the viewpoint of the default Admin account, we have the isolation and virtualization expected when using a sandbox. [/QUOTE]

Verification