Windows only. Tested on Mozilla. 1.) Connect to https://junruh.mcom.com:3002/ciphers.html 2.) You will not be able to connect since this cipher is not supported by Mozilla, but are given no warning that you cannot connect. What is expected: The warning present in Linux "Netscape and this server cannot communicate securely because they have no common encryption algorithms." What I get: Nothing happens.

mark, how is this obtained? do I need to check that pickled status (for what?)?

Do we know what happens with PSM for 4.x? John, can you check out that case with PSM 1.1? If 4.x doesn't do the right thing, reassign this to ddrinan.

Adding junruh to cc list since bugzilla said it didn't email him.

With 4.73 and PSM 1.1, I get "Netscape and this server cannot communicate securely because they have no common encryption algorithms."

mark, thoughts?

*** Bug 33843 has been marked as a duplicate of this bug. ***

Putting on [nsbeta2-] radar. Not critical to beta2. Do not think it will be that impt for users on beta. Please clear [nsbeta2-] in Status Summary if anyone feels differently and explain why.

Reassigning to javi during dougt's absence for the next three weeks.

*** Bug 31185 has been marked as a duplicate of this bug. ***

Adding nsbeta2 keyword to bugs with nsbeta2 triage value in status field so the queries don't get screwed up

marking nsbeta3- because of the infrequency with which this should happen.

*** Bug 56399 has been marked as a duplicate of this bug. ***

rtm

YOu can try www.elance.com and go to "My Elance". Same error. I don't even get warning that I'm switching to secure connection - maybe because link start with http, not https. This makes many e-commerce sites unusable.

I have no problem reaching "My elance" on Win98, Mac or Linux. For Win and Linux, make sure you have PSM installed. http://docs.iplanet.com/docs/manuals/psm/psm-mozilla/

We won't have a fix in time for 6.0. deleting "rtm" from keywords

*** Bug 57640 has been marked as a duplicate of this bug. ***

Same happens when you try to connect to http://comhome.comdirect.de/, see bug 57640 for details.

*** Bug 61494 has been marked as a duplicate of this bug. ***

If bug 61494 is a dup of this, this bug has a cousin: mostfreq bug 47617 "Connection to https needs to tell user to install PSM if w/o

nsbeta1

*** Bug 67022 has been marked as a duplicate of this bug. ***

new target milestone

Mass changing of product. Browser:Security:Crypto --> PSM 2.0

Milestone 2.0.

Don't think this will get done by 0.9.1 :(

->p2

junruh: junruh.mcom.com:3002 web server serving ciphers.html page provided as test case doesn't exist anymore.

If you have TLS turned on, you can use this TLS intolerant site - https://secure.customersvc.com/servlet/Show?WESPAGE=fo/home.html&MSRSMAG=FO You won't be able to connect, and won't know why.

After I land the patch in Bug 64888, that site will work. (I've tested it and with the patch, it loads).

You can also turn off SSL3 and try any of the SSL3 only sites on the cipher testing page. - http://junruh.mcom.com/ciphers.html - You cannot connect and won't know why.

ddrinan, please review my patch.

r=mcgreer

sr=blizzard

a= asa@mozilla.org for checkin to the trunk. (on behalf of drivers)

patch checked in.

Reopening. Mostly fixed, except in this case. 1.) Turn off TLS, leaving SSL2 and SSL3 on. 2.) Visit a TLS only site - https://junruh.mcom.com:5001 What is expected: A warning that a connection is not possible. What happens: No warning, you just can't reach the site.

Not sure if we'll be able to fix that case because the error we get back is PR_END_OF_FILE_ERROR, which doesn't seem like we can automatically assume there was a TLS inter-op error every time we see that error.

PDT for PSM

Mass reassigning target to 2.1

Failure->P1

P1

Marking fixed. I get a warning whenever I cannot reach a site.

are you sure you've tested with a tls only site and tls turned off? Reopening.

That's the only case that I can think of, and I've never found a real world site like that. It's only use would be to exclude Navigator browsers. I think this bug should be marked fixed, and open a new bug on that specific case. "Cannot reach a TLS only site with TLS disabled." Here is a TLS only server - https://junruh.mcom.com:5001

I just tried to connect to junruh.mcom.com:5001 with or without TLS enabled and I get a connection refused message. The server may not be up.

The server is up now.

Mass assigning QA to ckritzer.

Since our test server is probably the only server in the world that runs TLS *only*, I think we can put this off for a future release since the chance of a user actually running into this situation is practically zero.

Update the summary to reflect that the problem only occurs when TLS is turned off and the site only accept TLS connections. Moving to future. This is so rare, and the only organizations that would want to use a TLS only site would probably require that their user enable TLS in their browser.

Marking fixed. I get a warning now stating that there are no encryption algorythms in common. The new test site is https://pki.mcom.com:6050/tests.html

Verified.