on 9/14/01 7:14 PM, Eric Rescorla at [EMAIL PROTECTED] wrote:

> Just because the client sends a bogus CSS message, why would this
> cause the server to do so? I'm wondering if you have a networking
> problem. Did you collect these traces with a sniffer or via your
> program? If you did so via your program, the first thing to
> do is use a sniffer. I'd see what you get with ssldump and perhaps
> also with tcpdump--since ssldump doesn't know what to do with
> really anomalous PDUs--though perhaps it should.

I collected these via a program called OTSessionWatcher (which is analogous
to tcpdump in the MacOS 9 world).  The server is running on MacOS X, of
course.

I get the same error connecting from other client machines using Netscape
4.7, but not if I use 4.7.5.  There's clearly a bug in Netscape 4.7 and
earlier versions, but why is it just affecting our implementation of
OpenSSL?

I'll try to get a complete session with tcpdump for you.


cjh


================================================================
CJ Holmes, Director of Engineering                [EMAIL PROTECTED]
4D, Inc.                                      http://www.4D.com/
              4D Server v6.7.5 and Mac OS X
               "When the Solution Matters"

(Now Shipping!)  http://www.4D.com/675  (FREE to 4D v6.7 Owners)
================================================================


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to