Recent Posts61
ReHIPS / Re: Is there a conflict with sandboxie?
« Last post by fixer on December 15, 2019, 08:52:30 am »Welcome back, nick 
Basically ReHIPS isolates in the following way. For every isolated program it creates a custom restricted Windows user called ReHIPSUser. Each time this program is started it's started from this restricted user. By Windows security model other users (ReHIPSUser in our case) can't access private data (files, folders, registry, etc.) or affect programs of other users (other ReHIPSUser-s or real user, the one you use). And because it's a simple user (not Admin) it can neither affect the System. This is the first level and basic level of isolation. Some other levels are also in place, but they mostly tighten this concept than bring something drastically new.
So basically no, isolated programs don't have virtualized registry. They have their own registry hive and simply can't access real user registry hive or write to system parts of the registry. And the same goes for file system objects.
Basically ReHIPS isolates in the following way. For every isolated program it creates a custom restricted Windows user called ReHIPSUser. Each time this program is started it's started from this restricted user. By Windows security model other users (ReHIPSUser in our case) can't access private data (files, folders, registry, etc.) or affect programs of other users (other ReHIPSUser-s or real user, the one you use). And because it's a simple user (not Admin) it can neither affect the System. This is the first level and basic level of isolation. Some other levels are also in place, but they mostly tighten this concept than bring something drastically new.
So basically no, isolated programs don't have virtualized registry. They have their own registry hive and simply can't access real user registry hive or write to system parts of the registry. And the same goes for file system objects.
