s|b wrote:

> VanguardLH wrote:
> 
>> HTTPS scanning is way too slow in Avast.
> 
> I can't say I've noticed this. Maybe it's because I'm running W7 HP
> x64 SP1 on a SSD, I don't know? I have a cable connection, 30Mbps
> d/l; 3Mbps u/l, does that make much difference?

The [part of the] program doing work doesn't run off of storage media.
It is loaded in system memory and runs from there.  CPU and memory
speeds are more relevant.  I have 50 Mbps downstream.

>> If you didn't notice it, web surfing gets a l-o-t slower when Avast's
>> HTTPS scanning is enabled.
> 
> Haven't noticed this and I have the HTTPS Everywhere add-on installed in
> Fx. Which site(s) and which browser(s) did you use to make a comparison?

That add-on has NOTHING to do with encryption.  That only tries to
connect to an HTTPS version of a web page *if* available.

>> Until
>> Avast severely speeds up their HTTPS content interrogation process, it
>> is way too slow.  You might start to think your ISP halved your
>> bandwidth or something you installed or configured screwed up your
>> network traffic to slow it down.
> 
> Nope.

You are lucky.  Read their forums.  I'm not alone.

>> The proxy will get changed to 127.0.0.1 (no port assigned).
> 
> Doesn't happen here.

How often do you check if IE is using a proxy or not?  Did you check
immediately after you got the "page can't be displayed" error in IE?

>> By the way, if you get into the local certificate manager (certmgr.msc)
>> and do not find Avast's root certificate then that is the cause of the
>> "authenticity" error. 
>> 
>> So run certmgr.msc to see if Avast's cert was added.  
> 
> It's there alright. Says something about 'Server Authentication '.

Then the problem with non-connectivity is Avast's transparent HTTPS
proxy went unresponsive.  When proxies go dead, usually you have to kill
the process and reload it (which may require more than one process kill
and then loading them in the correct order).  Typically the cure is to
shutdown Windows and reboot.
--- NewsGate v1.0 gamma 2