Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: gate1975mlm on March 28, 2005, 03:33:51 AM
-
I know that Sygate does not really work at its best when running with Avast. But what about Kerio 4?
-
Sygate works fine with Avast. Don't know about Kerio.
-
I mean there is a known Problem when using Sygate and Avast Web Shield.
-
Kerio 4 does not have the problem of lack of recognition of proxies. So far, I have not found a problem that is accentuated by avast! But the Sygate problem is also manageable if you are careful in your configuration and reasonably observant. Try both, since they are free, and see which makes you more comfortable. I plan to stick with Kerio unless I find something unusual-have only been trying it out for the past month or so. If you have not done so yet, for Sygate information see the thread http://www.dslreports.com/forum/remark,13003405~mode=flat~days=9999 .
-
I've tested Sygate both incoming and outgoing and there is not an issue that I can see. In other words, Sygate passes the normal incoming tests and the outgoing LeakTest, which what Sygate was passing before I installed Avast and related Webshield.
I don't think Avast coupled with Sygate is increasing security risk. If someone needs to correct me or elaborate further than please do. I may be incorrect.
-
I can confirm that there's no problem with Kerio 4.1.2. and WebShield.
Applications seeking to connect to the internet are not not allowed to do so until permission is given (assuming of course that your connection rule is 'ask'.)
Here's Kerio doing just that:
(http://donaldbroatch.users.btopenworld.com/kerioalert.jpg)
-
I confirm that too ;)
-
I am using Kerio personal firewall 4 and avast! 4.6(4.6.623), never had any problems with these two software.
-
I know that Sygate does not really work at its best when running with Avast. But what about Kerio 4?
I can only see a problem with Sygate (free): the internal bug/problem of local proxy and outbound connections discussed a lot here.
Except this, Sygate is very stable and nice firewall working with avast.
Kerio always worked with avast too... ;)
-
I can confirm that there's no problem with Kerio 4.1.2. and WebShield.
Applications seeking to connect to the internet are not not allowed to do so until permission is given (assuming of course that your connection rule is 'ask'.)
Here's Kerio doing just that:
(http://donaldbroatch.users.btopenworld.com/kerioalert.jpg)
I see. Well, I almost always keep Sygate's permission for the browsers not to ask so I would never get a warning regardless. So, it's an outbound traffic problem with Sygate. I understand. Thanks to all who contributed. To this subject. Not the problem with Sygate. Sygate should fix this. I take it they are not or not in a big hurry.
-
As has been replied already, WebShield works really nice with Sygate.
For other programs you do get asked if wanting guys.
It is very bad when a user like 'gate...' comes in here to say something of what
Mixing some heresay or other local proxy concerns when it is not so with WebShield.
He has obviously no own experience, or at least not cared to test.
Here are for the same program A2 antitrojan the guestions frim SPF:
-
Actually, if you set your browser to ask for permission with webshield on and Sygate running you won't get an alert from Sygate that the browser needs permission. Yes, sygate will ask if other programs trying sending out, thus passing the LeakTest. But not the browsers even if you set Sygate to ask permission for the browser programs. I don't know how much of a security risk this is, if any.
As Technical mentioned above, it is known problem within SYGATE and not Avast.
-
Not the problem with Sygate. Sygate should fix this. I take it they are not or not in a big hurry.
Well, it's too much time for a repair... More than one year as I heard... Shame on Sygate...
-
Actually, if you set your browser to ask for permission with webshield on and Sygate running you won't get an alert from Sygate that the browser needs permission.
Most people would propably have an allow client access normally for their browser.
Also if you further set a manual proxy setting for the browser you normally surf with and blank the redirection port field in webshield, then no other browser even use the webShield.
-
Not the problem with Sygate. Sygate should fix this. I take it they are not or not in a big hurry.
Well, it's too much time for a repair... More than one year as I heard... Shame on Sygate...
Yes I agree! Could someone at Avast contact Sygate about this?
-
Yes I agree! Could someone at Avast contact Sygate about this?
Unfortunately I don't believe that contacting any person from Sygate team would provide sufficient code changes in their firewall code....
-
Actually, if you set your browser to ask for permission with webshield on and Sygate running you won't get an alert from Sygate that the browser needs permission.
Most people would propably have an allow client access normally for their browser.
Also if you further set a manual proxy setting for the browser you normally surf with and blank the redirection port field in webshield, then no other browser even use the webShield.
If I understand you correctly than there shouldn't be a problem with Sygate not recognizing the browser client if Sygate is set not to ask permission for the browser.
Also, the redirection port field in Webshield is not available on Win98.
-
I see no reason why you should not use WebShield with SPF, Culpeper?
All the browser HTTP 80 TCP connections still get logged as an ashWebSv.exe enties.
I am not using Win98, but I have understood that it works like the redirected port was already blanked. So you have to use a manual proxy, and this I think is s good thing.
-
I'm sticking with Sygate Pro. I like the icon in the task bar.
-
I see no reason why you should not use WebShield with SPF, Culpeper?
All the browser HTTP 80 TCP connections still get logged as an ashWebSv.exe enties.
I am not using Win98, but I have understood that it works like the redirected port was already blanked. So you have to use a manual proxy, and this I think is s good thing.
I use Sygate PFW Pro.
Not to beat a dead horse..... :-X
So the fix is to remove the port 80 from Avasts webshield and set up a manual proxy on my FireFox web Browser?
Or just disable Webshield alltogether?
-
Just use Sygate with Webshield with the manual setup in the browser. Don't worry about Webshield settings.