Cracker Classifieds - Cracker free ads & forums


 

  • search for
  • in
spacer

Refine your search

Up one level.
 


Advertisement
Advertisement

Most popular in
Cracker

Latest posts in
Hospitality / tourism

 

coogiwarehouse at 11:25 AM - 28/08/2009

paypal shoes versace clothing versace t shirt gucci t shirt gucci clothing dolce gabbana shoes lrg ... more

 

bibibobo144 at 6:10 PM - 27/08/2008

FireFox 3 triggers an OpenSSL bug... more

FireFox 3 triggers an OpenSSL bug


bibibobo144's avatar

Posted by: bibibobo144
Viewed: 1546
Date Posted: 27/08/2008 - 6:10 PM
Thread ID: 236591
Rating (1)
Your rating
1
2
3
4
5
Email a friend

FireFox 3 triggers an OpenSSL bug

June 22nd, 2008 Secure Connection Failed An error occurred during a connection to xyz-abe.com SSL received an unexpected Change Cipher Spec record. (Error code: ssl_error_rx_unexpected_change _cipher)

I’ve been seeing more and more customers report this in the lead up to FireFox 3 going live…now the release has come I think the only thing you can do is try and get your production servers upgraded to the latest OpenSSL (0.9.8h) as soon as possible. Unfortunately the only other work around involve users disabling something in about:config or disabling SSLv3 on your server.

Some background reading on the bug:

Original report

Mozilla bug report

OpenSSL fix

Additionally I’ve seen FireFox 3 introduce another bug related to incorrectly signed HMAC codes in SSL transactions. After some digging around I noticed that FireFox 3 supports the Camellia cipher which AFAIK isn’t widely supported amongst other browers yet. During SSL negotiation the browser seems to end up using Camellia even though it could have negotiated the more familiar AES cipher. I hacked around this in one clients nginx configuration by adding the following to their http//:www.vipsofts.com - DOWLOAD +KEY.








0 comment(s) on this listing



Make a comment


You need to be logged in and have your primary email verified in order to post comments.
Please login or register.