Reply to thread

Message

<blockquote data-quote="Recrypt" data-source="post: 708256" data-attributes="member: 22989">1. I agree, it&#039;s possible to mess something up. In the end, it&#039;s up to the user to follow the best practices. User being the final and ultimate judge can just disable the security and no product can protect from it. What I mean is ReHIPS is trying to provide a way for security, but it&#039;s up to the user to follow that way and yeah, sometimes it requires knowledge and not that easy as we&#039;d like it to be, but that&#039;s why we&#039;re here and we&#039;re working on it <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />2. Exploiting the isolated program will grant basically the same rights and privileges as something executed in the same isolated environment. So it&#039;ll have no access to real user profile. And will have access to at most 1 document in C:\ReHIPS subfolder.3. I agree, it can gather some information, but will it be a security incident? All sensitive data should be stored in real user profile, malware will have no access to it. It can read public and already well-known files from Windows directory, from Program Files directory, it&#039;ll probably learn that I have for example Opera installed. Maybe it&#039;s not comfortable to know that this information left PC, but it doesn&#039;t look critical.And I see there is a discussion of Open File Access feature. It&#039;s described in this blogpost <a href="https://forum.rehips.com/index.php?topic=9484.0" target="_blank">[FAQ] Convenient yet treacherous Open File Access feature</a>In short words: it&#039;s not recommended to rely on it, it&#039;s more of a &quot;workaround&quot; for usability. But if you indend to build a secure and reliable system, it&#039;s preferred to disable it.But what you see as a real user will be slightly different for isolated programs. For example I say that isolated programs don&#039;t have any access to real user profile. When you browse there in explorer and double-click on some document, Open File Access feature kicks in and does some magic for the isolated program to successfully access the document. But isolated programs can&#039;t do it on their own, this magic won&#039;t work for them. When they try to browse real user profile folder (or registry hive) they&#039;re transparently redirected into their own isolated (ReHIPSUserX) profile folder (or registry hive) and can see and access only files from there.Best regards, fixer.</blockquote>

[QUOTE="Recrypt, post: 708256, member: 22989"] 1. I agree, it's possible to mess something up. In the end, it's up to the user to follow the best practices. User being the final and ultimate judge can just disable the security and no product can protect from it. What I mean is ReHIPS is trying to provide a way for security, but it's up to the user to follow that way and yeah, sometimes it requires knowledge and not that easy as we'd like it to be, but that's why we're here and we're working on it :) 2. Exploiting the isolated program will grant basically the same rights and privileges as something executed in the same isolated environment. So it'll have no access to real user profile. And will have access to at most 1 document in C:\ReHIPS subfolder. 3. I agree, it can gather some information, but will it be a security incident? All sensitive data should be stored in real user profile, malware will have no access to it. It can read public and already well-known files from Windows directory, from Program Files directory, it'll probably learn that I have for example Opera installed. Maybe it's not comfortable to know that this information left PC, but it doesn't look critical. And I see there is a discussion of Open File Access feature. It's described in this blogpost [URL="https://forum.rehips.com/index.php?topic=9484.0"][FAQ] Convenient yet treacherous Open File Access feature[/URL] In short words: it's not recommended to rely on it, it's more of a "workaround" for usability. But if you indend to build a secure and reliable system, it's preferred to disable it. But what you see as a real user will be slightly different for isolated programs. For example I say that isolated programs don't have any access to real user profile. When you browse there in explorer and double-click on some document, Open File Access feature kicks in and does some magic for the isolated program to successfully access the document. But isolated programs can't do it on their own, this magic won't work for them. When they try to browse real user profile folder (or registry hive) they're transparently redirected into their own isolated (ReHIPSUserX) profile folder (or registry hive) and can see and access only files from there. Best regards, fixer. [/QUOTE]

Verification