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
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
Other security for Windows, Mac, Linux
AppGuard v6 lock down anomaly?
Message
<blockquote data-quote="simmerskool" data-source="post: 1019638" data-attributes="member: 61091"><p>I got a reply from AG support shortly after I provided my license no. So AG support seems responsive to help question emails. The premise of my question was wrong! Support says:</p><p></p><p>"It is NOT user space in location "C:\appxxx\"</p><p>This is System Space which will allow the launch.</p><p>If you wanted to define a System Space location to the policy as User Space you</p><p>would add it to the User Space Policy and toggle to YES to include it in the User</p><p>Space Policy.</p><p>Default User Space locations </p><p>User profiles "C:\Users\Username\*"</p><p>C:\ProgramData\*</p><p>UserSpace allows write to folders but restricts launch</p><p>SystemSpace prevents Guarded Application writes but allow launch</p><p>More information is included in the built in help system with Solo."</p><p></p><p>Assuming AG help pdf is correct and written clearly, then somewhat of a cross-wiring in my thinking. IT happens <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite120" alt="o_O" title="Er... what? o_O" loading="lazy" data-shortname="o_O" /> The "scary" part is I had the help file open and was reviewing when I wrote the first post in this thread.</p><p>But I am still foggy: isn't the conclusion or implication to Support's email that any exe in root directory ("system space") will run even if the exe is unsigned and not otherwise previously allowed?? Does that compute? or do I continue to mis-read. Weekend plans, RE-READ the AG manual. </p><p></p><p>So the app I was running from c:\root SystemSpace was not a Guarded App, was unsigned, AG prevented "writes" but allowed to launch. So could be, I did run this app previously, and had turned off read / write notifications which is why I saw nothing in AG Activity Log for this event. Certainly possible. This app did run and did display correct info onscreen, but apparently was blocked from writing anything to hdd/ssd. Just because I'm foggy... I sitll like AG (for now). I guess that any app that default installs out of \program files\ thows me a curve ball. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite120" alt="o_O" title="Er... what? o_O" loading="lazy" data-shortname="o_O" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite132" alt=":unsure:" title="Unsure :unsure:" loading="lazy" data-shortname=":unsure:" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite119" alt=":rolleyes:" title="Roll eyes :rolleyes:" loading="lazy" data-shortname=":rolleyes:" /></p></blockquote><p></p>
[QUOTE="simmerskool, post: 1019638, member: 61091"] I got a reply from AG support shortly after I provided my license no. So AG support seems responsive to help question emails. The premise of my question was wrong! Support says: "It is NOT user space in location "C:\appxxx\" This is System Space which will allow the launch. If you wanted to define a System Space location to the policy as User Space you would add it to the User Space Policy and toggle to YES to include it in the User Space Policy. Default User Space locations User profiles "C:\Users\Username\*" C:\ProgramData\* UserSpace allows write to folders but restricts launch SystemSpace prevents Guarded Application writes but allow launch More information is included in the built in help system with Solo." Assuming AG help pdf is correct and written clearly, then somewhat of a cross-wiring in my thinking. IT happens o_O The "scary" part is I had the help file open and was reviewing when I wrote the first post in this thread. But I am still foggy: isn't the conclusion or implication to Support's email that any exe in root directory ("system space") will run even if the exe is unsigned and not otherwise previously allowed?? Does that compute? or do I continue to mis-read. Weekend plans, RE-READ the AG manual. So the app I was running from c:\root SystemSpace was not a Guarded App, was unsigned, AG prevented "writes" but allowed to launch. So could be, I did run this app previously, and had turned off read / write notifications which is why I saw nothing in AG Activity Log for this event. Certainly possible. This app did run and did display correct info onscreen, but apparently was blocked from writing anything to hdd/ssd. Just because I'm foggy... I sitll like AG (for now). I guess that any app that default installs out of \program files\ thows me a curve ball. o_O:unsure::rolleyes: [/QUOTE]
Insert quotes…
Verification
Post reply
Top