I have been an Outpost fan for awhile. I am now playing with Comodo.
I like it so far for the small footprint and pretty easy setup to get rolling.
I am not so far impressed with it’s user interface as much as I had hoped.
Developers, I know you have more than enough to do. I know you have looked at
various products and tried to balanced the best of all into your package. I know this. I do it as well.
My advice for developers would be to get a copy of the original Outpost Free v1.0. Yes, it is dated.
Yes, you do have to know something to use it. No, it does not monitor as much, just an exe and traffic.
BUT… the best features about it are the simple ones, that I find lacking in Comodo.
DNS plugin - resolve and cache. very usefull for seeing where an app is actually going.
Ads and active content plugin – c’mon, who doesn’t like a little ad filtering?
the ability to save your configurations (ok, that is in the pro version, but still…)
pretty simple interface. I know, with bigger rigs, peeps want more eyecandy. oh well.
best of all, the presets. a file, preset.lst, into which I can put every last one of my configurations
for each and every application that may try to go online. I can copy/paste it to others machines and
then they have the same rulesets. THAT is a must for those of us who really like to take control of OUR computers.
unless I have missed something, the layering of rules for a certain application is not possible?
I have the latest version, as of Sept 1st anyway. I use the proxomitron. CF found it. I allowed it.
There is a rule for both tcp and udp. OK. I want to now give it more fine tuning. I find that I cannot
add another layer of rules for it. For example, in my OP config I would have the following for it
[Proxomitron] VisibleState: 1 Exe: Proxomitron, proxomitron.exe DefaultState: 1 RuleName: Proxomitron HTTP Access Protocol: TCP Direction: Outbound RemotePort: 80 AllowIt DefaultState: 1 RuleName: Proxomitron DNS Resolution 1 Protocol: UDP RemoteHost: 216.x.x.x RemotePort: 53 AllowIt DefaultState: 1 RuleName: Proxomitron DNS Resolution 2 Protocol: UDP RemoteHost: 216.x.x.x RemotePort: 53 AllowIt DefaultState: 1 RuleName: Proxomitron DNS Resolution 3 Protocol: UDP RemoteHost: 216.x.x.x RemotePort: 53 AllowIt DefaultState: 1 RuleName: Proxomitron Block DNS (TCP) Protocol: TCP Direction: Outbound RemotePort: 53 BlockIt
And that pretty much takes care of what proxomitron can and can’t do.
Of course the browser then needs a rule set, which looks like this
[Opera] VisibleState: 1 Exe: Opera, opera.exe DefaultState: 1 RuleName: Opera Access to Proxomitron Protocol: TCP Direction: Outbound RemotePort: 8080 AllowIt DefaultState: 1 RuleName: Opera FTP connection Protocol: TCP RemotePort: 21 Direction: Outbound AllowIt DefaultState: 1 RuleName: Opera FTP DATA connection Protocol: TCP RemotePort: 20 Direction: Inbound AllowIt DefaultState: 1 RuleName: Opera FTP Data (Passive) Protocol: TCP RemotePort: 1025-65535 Direction: Outbound AllowIt
The result is that opera requests only things that are not port 80, which proxomitron handles.
DNS is taken care of per application. I have allow and disallow DNS rules as well.
The best part of the old Outpost (which I still use, don’t care for the new ones) is that you
can set it up pretty darn complex and tight, and then save it. Edit it when you bring new
apps onboard and save it to all your OP firewall machines.
Comodo appears to be the only viable alternative I would use at this time. I sincerely hope that the
HYPE that is in this forum about really listening to the peeps using it are really true.
Maybe I am a lone duck in a big pond, but I would certainly be more than happy to see a very complicated method
of setting up my custom rules (presets) that I could happily choose to apply to the associated application when it shows itself.
No gripes, just observations from a geek.