Nelson Bolyard wrote:
Jean-Marc Desperrier wrote:
Of these, I would say that TLS hello extensions have experienced the
most problems, due to servers that do not ignore them (which the RFCs
require) and instead reject the connections.
Interesting, I didn't know it was alredy sent by default.
T
> - It can be quite difficult for someone who is not familiar with the
> code to interpret. The feature exists to help the code's developers
> debug the code, not as a general SSL line monitoring tool (which
> ssltap is).
>
ok...I see. I apologize to Pedro then, I am more of a developer than
a
Peter Djalaliev wrote:
> To enable the SSL debugging statements, you need to set the SSLTRACE
> environment variable. Possible values are 0-60 (0=no dubugging,
> 60=lots)
The maximum value is 127, IIRC. However, it may be that presently
we are not using values larger than 60.
I specifically di
Jean-Marc Desperrier wrote:
> The main difference between Fx 2 and Fx 1.5 is that 56 bits ciphers are
> now by default disabled.
That is one of the big differences.
IINM, other big differences include:
- SSL2 support disabled, client hellos are now SSL3, not SSL2.
- Added support for TLS hello
Hello,
To enable the SSL debugging statements, you need to set the SSLTRACE
environment variable. Possible values are 0-60 (0=no dubugging,
60=lots)
If this doesn't work for you (I suppose it depends on your embedding
environment), you can place PR_LOG statements within the NSS's SSL
code. To g
Our device implements the following ciphers:
#define USE_SSL_RSA_WITH_RC4_128_MD5
#define USE_SSL_RSA_WITH_RC4_128_SHA
#define USE_SSL_RSA_WITH_3DES_EDE_CBC_SHA
#define USE_TLS_RSA_WITH_AES_128_CBC_SHA /* must define USE_TLS */
#define USE_TLS_RSA_WITH_AES_256_CBC_SHA /* must define USE_TLS */
Pedro DeKeratry wrote:
The company I work for produces an embedded device that contains an
SSLv3/TLSv1.0 implementation.
> [...] Firefox 2.0.x does not. The browser sends a
RST at the end of nearly every initial SSL handshake.
Do you have a list of the ciphers you implement in your device ?
Pedro DeKeratry wrote:
> Hi,
>
> The company I work for produces an embedded device that contains an
> SSLv3/TLSv1.0 implementation. Firefox 1.5.x performs HTTPS just fine
> with our device, however, Firefox 2.0.x does not. The browser sends a
> RST at the end of nearly every initial SSL handshake
Hi,
The company I work for produces an embedded device that contains an
SSLv3/TLSv1.0 implementation. Firefox 1.5.x performs HTTPS just fine
with our device, however, Firefox 2.0.x does not. The browser sends a
RST at the end of nearly every initial SSL handshake.
How do I enable SSL debugging o
9 matches
Mail list logo
