265346 - On Secure server wouldnt access as ' didnt have any algorithms in common'

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Martyn Fox]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

Tryed to order off amazon.co.uk but wouldn't authenticate onto secure server due
to not having any algorithms in common. Worked on previous version of
firefox(0.9.1) and worked in IE when used

Reproducible: Always
Steps to Reproduce:
1.Pick product
2. Go to checkout, login
3. try to click on any link

Actual Results:  
message box saying couldn't authenticate with secure server as no algorithms in
common

Expected Results:  
sent and recieved data over the secure server

Comment 1

[Tom Ward]

Just experienced this bug on Firefox 1.0PR as have a few other people
http://pinksocks.co.uk/2004/10/20/firefox-and-amazoncouk/
http://forums.freddyshouse.com/archive/index.php/t-36785.html
http://www.ufaq.org/modules.php?name=Forums&file=viewtopic&p=10513

Sometimes reproducable, but not consistently. My events:
- Failed to log in to amazon.co.uk ("No common encryption algorithms")
- Logged in to bugzilla securely in a new tab
- switched back to amazon.co.uk tab to replicate, then it successfully logged in
securely
- restarted firefox
- failed to log in to amazon.co.uk
- restarted firefox
- logged in successfully to amazon.co.uk

I have SSL2, SSL3, TLS enabled, but not OCSP.

Maybe it's significant that the reports so far are only from amazon.co.uk and
amazon.de - none from amazon.com.

Is anyone looking at this bug? I don't want to convince all my friend's parents
if they're going to hit this. 

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.