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
Security
Video Reviews - Security and Privacy
Comodo Firewall 10 Setup
Message
<blockquote data-quote="AtlBo" data-source="post: 668057" data-attributes="member: 32547"><p>ncage...</p><p></p><p>Rather than answer your questions all at once here, here are some thoughts to consider. Let me start with a quote from you:</p><p></p><p></p><p></p><p>Couldn't have put it better. You will find the help will become more valuable as you work through things, but it took me a year or so before I would have said this was true for me. Next, this might help you pick things up more quickly. Comodo settings aren't going to make perfect sense to you. This is because they don't make 100% sense in the first place. There isn't anything per se missing but there are quirks.</p><p></p><p>The privileges escalation setting does not turn off UAC. It does seem to indicate this the way it is worded, but it is not the case. Basically, if you choose to show the alert for apps that want raised privileges, the options you get on the alert are the same ones you see listed in the setting. I recommend unchecking the box and then simply do not choose to remember your choice to disallow/allow privilege escalation for a given executable (unless you are sure it should be blocked). Then you can choose to remember the choice. These don't happen very oftenly. By far most things you run will be auto-allowed because of the "Trusted Vendor" list.</p><p></p><p>Run Unlimited v Run Unlimited and Trust->basically the same thing but the latter adds the rating of "Trusted" to the executable in the "File List" in the settings. This means no element of Comodo will be monitoring the executable. Anyway, I recommend staying away from this setting. Just uncheck the box. Also, on the various types of alerts (Firewall/HIPS/Containment) I recommend staying away from designating (and remembering) an executable as a type (i.e "Allowed" or "Installer" etc.). These settings can cause you consternation later when you go through your rules. Keep it simple and block or allow and remember if you are 100% sure and you can safely run Proactive with HIPS on no problem.</p><p></p><p>The privilege elevation alerts btw, will not stop Auto-containment from happening. On first run of an executable that is not auto-allowed, you will get both alerts. For me, it behaves more like an extra HIPS alert, although I admit remembering a choice I suppose would lead to de-containing an executable the second time it runs.</p><p></p><p>On [USER=7463]@cruelsister[/USER]'s settings I think it's a good place to start, but I like HIPS. For me, this means also making some other adjustments to her settings to limit my opportunities for accidently creating "Trusted" in the "File List" Mostly, I gear my thinking to allow or block without remembering, unless I am 100% sure of my choice. In that case, then fine, remembering that an allow will create "Trusted" status in the "File List". Cruelsister eliminates HIPS but she also chooses to trust the Comodo system by not seeing alerts for privilege escalation (I think firewall too). That's fine, and it works extremely well too, but I like the extra layer HIPS provides, since I might take a chance at some point.</p></blockquote><p></p>
[QUOTE="AtlBo, post: 668057, member: 32547"] ncage... Rather than answer your questions all at once here, here are some thoughts to consider. Let me start with a quote from you: Couldn't have put it better. You will find the help will become more valuable as you work through things, but it took me a year or so before I would have said this was true for me. Next, this might help you pick things up more quickly. Comodo settings aren't going to make perfect sense to you. This is because they don't make 100% sense in the first place. There isn't anything per se missing but there are quirks. The privileges escalation setting does not turn off UAC. It does seem to indicate this the way it is worded, but it is not the case. Basically, if you choose to show the alert for apps that want raised privileges, the options you get on the alert are the same ones you see listed in the setting. I recommend unchecking the box and then simply do not choose to remember your choice to disallow/allow privilege escalation for a given executable (unless you are sure it should be blocked). Then you can choose to remember the choice. These don't happen very oftenly. By far most things you run will be auto-allowed because of the "Trusted Vendor" list. Run Unlimited v Run Unlimited and Trust->basically the same thing but the latter adds the rating of "Trusted" to the executable in the "File List" in the settings. This means no element of Comodo will be monitoring the executable. Anyway, I recommend staying away from this setting. Just uncheck the box. Also, on the various types of alerts (Firewall/HIPS/Containment) I recommend staying away from designating (and remembering) an executable as a type (i.e "Allowed" or "Installer" etc.). These settings can cause you consternation later when you go through your rules. Keep it simple and block or allow and remember if you are 100% sure and you can safely run Proactive with HIPS on no problem. The privilege elevation alerts btw, will not stop Auto-containment from happening. On first run of an executable that is not auto-allowed, you will get both alerts. For me, it behaves more like an extra HIPS alert, although I admit remembering a choice I suppose would lead to de-containing an executable the second time it runs. On [USER=7463]@cruelsister[/USER]'s settings I think it's a good place to start, but I like HIPS. For me, this means also making some other adjustments to her settings to limit my opportunities for accidently creating "Trusted" in the "File List" Mostly, I gear my thinking to allow or block without remembering, unless I am 100% sure of my choice. In that case, then fine, remembering that an allow will create "Trusted" status in the "File List". Cruelsister eliminates HIPS but she also chooses to trust the Comodo system by not seeing alerts for privilege escalation (I think firewall too). That's fine, and it works extremely well too, but I like the extra layer HIPS provides, since I might take a chance at some point. [/QUOTE]
Insert quotes…
Verification
Post reply
Top