Sir:

me@privacy.net wrote:
> I had profile problems and had to create a new profile with Peter's
> SeaMonkey build on one of my systems. I am now seeing something off when
> I goto secure sites on this system. The icon in the lower right of the
> browser is a broken red lock and clicking on it reveals a page showing
> "Connection partially encrypted" in the security tab of the page info.
> Loading the same page in the same browser on another of my systems shows a
> solid green lock and RC4 encryption in use!
>
> What can I do to correct the problem in the profile on the system not
> showing appropriate encryption? Is this a profile or SeaMonkey issue I am
> dealing with? This is Peter's latest build.
>

RC4 is a weak cyper. It is likely that the system that is failing to
connect is set to require higher level of encryption than RC4 and the
site is failing to agree with the higher requirements. On the other
hand the system that connects is set to use a lessor level of
encryption, like SSL 1 or SSL 2. The fix is to get the site to agree
with the higher level of encryption. But in the mean time, the work
around is to accept the lessor security of SSL 1 or SSL 2 and change the
failing system to accept it. IMHO, I would not change the failing
system and avoid the site until they upgrade their security.
--
Bill
Thanks a Million!

In <46a1a72d$0$16521$4c368faf@roadrunner.com>, on 07/21/2007
at 01:30 AM, "William L. Hartzell" said:

>me@privacy.net wrote:
>> I had profile problems and had to create a new profile with Peter's
>> SeaMonkey build on one of my systems. I am now seeing something off when
>> I goto secure sites on this system. The icon in the lower right of the
>> browser is a broken red lock and clicking on it reveals a page showing
>> "Connection partially encrypted" in the security tab of the page info.
>> Loading the same page in the same browser on another of my systems shows a
>> solid green lock and RC4 encryption in use!
>>
>> What can I do to correct the problem in the profile on the system not
>> showing appropriate encryption? Is this a profile or SeaMonkey issue I am
>> dealing with? This is Peter's latest build.

>RC4 is a weak cyper. It is likely that the system that is failing to
>connect is set to require higher level of encryption than RC4 and the
>site is failing to agree with the higher requirements. On the other
>hand the system that connects is set to use a lessor level of
>encryption, like SSL 1 or SSL 2. The fix is to get the site to agree
>with the higher level of encryption. But in the mean time, the work
>around is to accept the lessor security of SSL 1 or SSL 2 and change the
>failing system to accept it. IMHO, I would not change the failing
>system and avoid the site until they upgrade their security.

The problem disappeared after I closed the tab I was accessing the secure
sites from and opened a fresh tab to use . So I am unsure now what the
cause was, but it appears to be working properly now.

-- Dave
-----------------------------------------------------------
dhdurgeeverizonnet
-----------------------------------------------------------