Firefox encumbrance

[eman]

JUst been over to http://www.mozilla.org/projects/secu.../ssl_help.html

and found this:

SSL Protocol Versions

The Secure Sockets Layer (SSL) protocol defines rules governing mutual authentication between a web site and browser software and the encryption of information that flows between them. The Transport Layer Security (TLS) protocol is an IETF standard based on SSL. TLS 1.0 can be thought of as SSL 3.1.

You should normally leave both SSL checkboxes and the TLS checkbox selected in the SSL Preferences panel to ensure that both older and newer web servers can work with the browser.

Important note re TLS: Some servers that do not implement SSL correctly cannot negotiate the SSL handshake with client software (such as the browser) that supports TLS. Such servers are known as "TLS intolerant."

When the Enable TLS option in the SSL preferences panel is selected, the browser attempts to use the TLS protocol when making secure connections with a server. If that connection fails because the server is TLS intolerant, the browser will fall back to using SSL 3.0.
--------------------------

So there you go. It's a server problem - nothing to do with CCBill per se.

[MrYum]

Originally Posted by eman

JUst been over to http://www.mozilla.org/projects/secu.../ssl_help.html

and found this:

SSL Protocol Versions

The Secure Sockets Layer (SSL) protocol defines rules governing mutual authentication between a web site and browser software and the encryption of information that flows between them. The Transport Layer Security (TLS) protocol is an IETF standard based on SSL. TLS 1.0 can be thought of as SSL 3.1.

You should normally leave both SSL checkboxes and the TLS checkbox selected in the SSL Preferences panel to ensure that both older and newer web servers can work with the browser.

Important note re TLS: Some servers that do not implement SSL correctly cannot negotiate the SSL handshake with client software (such as the browser) that supports TLS. Such servers are known as "TLS intolerant."

When the Enable TLS option in the SSL preferences panel is selected, the browser attempts to use the TLS protocol when making secure connections with a server. If that connection fails because the server is TLS intolerant, the browser will fall back to using SSL 3.0.
--------------------------

So there you go. It's a server problem - nothing to do with CCBill per se.

Excellent...glad you found the answer

Oh Virgo...I have tried sheepskin...it ain't all it's cracked up to be

But I still think FF is pretty damn cool

[Simon]

Originally Posted by MrYum

I have tried sheepskin...it ain't all it's cracked up to be

Of course not ... people who want to fuck sheep should just go ahead and do it.

condomdepot text:

"Because it is made from a natural lamb skin membrane, you will find it has its own special feeling of sensitivity...although they are thick, they offer a feeling unlike any other condom and feel like you are NOT wearing a condom."

Right, they feel like you're fucking a natural lamb skin membrane.

Don't ask.

[raymor]

I've never had a problem with CCBill or any other SSL using the Mozilla browser, which is
the same rendering engine and everything as Firefox, just with more features.
For those of you who like Firefox, you might also want to try the Mozilla browser.
It has pretty much all of the same features as Firefox since it's based on the same
codebase, plus a lot of features that web professionals will like. Some people thought
it had too many features and should be simpler, so they took a lot of features out
and called it Firefox.