Hi,
I have been trying to get to grips with various comodo versions over the last year or so. Just when I think I might understand things, I discover that I don’t, and my brain hurts, so I go back to Sygate, which is comforting but perhaps a little too leaky these days!
I have now installed comodo version 3.0.18.309.
I did not install the full defence + but the receommended lesser setting.
At first I had Comodo in the train with safe mode, but I was unhappy that comodo allowed so many connections and I didn’t know what was going on. For example, programs like Winamp were connecting to the internet and I was not aware of this. Comodo seemed to allow them because they were “safe” whereas I’d like to be asked if I wanted to allow the connection.
So I changed my settings to custom mode. However as I use Proxomitron as a local proxy, I am bombarded with requests as I surf! Is there any way to have a happy medium where I get asked about programs like Winamp and Media Player, but don’t get 30 popups a second relating to permission for Proxomitron?
I’ve read several posts about rules for proxomitron in Comodo forums but I didn’t understand them all. Is there any simple guide anyone can point me to which will help me manage Comodo better? I have read a few guides, but they didn’t seem to cover what I wanted.
Any help or links to appropriate help would be very much appreciated.
Thanks,
Souzapet
+1. I use The Proxomitron (keeps ad. junk out quite well, although now I use Opera it’s not so necessary) but don’t really understand it.
As for Winamp etc., I don’t consider them as ‘safe’ (or IE, OE and the like).
OK, I watched and read all the comodo pop-ups about Proxomitron carefully, and then looked again at the other posts regarding rules (I think they applied to V2, but hopefully they would be similar for V3.*) and then tried a bit of DIY rule-making.
This has certainly stopped most of the pop-ups, but I would be grateful if someone could re-assure me that I haven’t done something silly and opened up my computer to all kinds of threats!
These are the rules I’ve made for Proxomitron
Allow TCP out from IP any where source port is in [1000-5000] and destination port is 80;
Allow TCP out from IP any where source port is in [1000-5000] and destination port is 443;
Ask TCP or UDP in/out from IP any where source port is any and destination port is not 80.
Any help is appreciated.
Thanks
Souzapet
I would just allow incoming connetions from localhost + other PCs you want to proxy, on the port you have prox listening on (8080)? Going out to port 80 (prox by defaut won’t filter SSL, though you can sort of hack it to)…
Then if you want to, you could limit your browser to connecting on port 8080 only to localhost - forcing any HTTP through prox, or fail…
Hi JP,
Thanks for your prompt reply, but unfortunately, I don’t really understand what you mean. I’m struggling with rules because I only understand a very little about computer protocols, etc.
If you could put what you say into a simple “rule” for me, I might be able to grasp it a little better.
I’m worried that the little knowledge I have might lead me to do dangerous things! Are the “rules” I’ve made so far not suitable? more importantly, are they dangerous? if you could give me better ones - based on what you posted before - I’d appreciate it.
Thanks,
Souzapet
Well, I guess it’s probably fine, I don’t have Comodo installed here to take a quick look but here’s my points.
If these are just for proxomitron, the “openness” of the rules doesn’t matter because it can’t really affect anything.
Usually I would change to this (again, in practice in this instance, it might not make a difference):
Allow TCP out from 127.0.0.1 where source port is any and destination port is 80
etc. However, I’m not sure of the source ports for prox, and I’m not sure why you used [1000-5000], if those are all that’s needed then that would be better. For prox I would probably not care what port it’s using as the source as that’s not an incoming port.
Again, I’d tell my browser to not use prox for HTTPS unless I’d set up prox to filter SSL. That is, in the network settings I’d set HTTPS to no proxy.
Are these rules only applied to proxomitron? I think comodo works like that, in that case you’re fine.
Thanks for the further explanation. I was basing the rules on the information I found in the link below - that’s where I got the port range from.
I have proxo set up to filter even secure HTTPS sites occasionally, so that’s why I included 443. I’ll change the source as you suggested, but thanks for letting me know that I haven’t done anything stupid.
Thanks,
Souzapet