RE: Comm Trace

Exactly. Thats why I said I had expected it although I thought there was
just a small possibility that comms trace may have de-crypted it for us..
However if that was the case then we would have cracked 128 bit security in
a rather easy way :-))

Regards

Ian Patterson
Grange Management Consultants
tel 01947 880458
www.grange-systems.co.uk




-----Original Message-----
From: midrange-l-bounces+ian=grange-systems.co.uk@xxxxxxxxxxxx
[mailto:midrange-l-bounces+ian=grange-systems.co.uk@xxxxxxxxxxxx]On
Behalf Of Scott Klement
Sent: 19 September 2003 16:25
To: Midrange Systems Technical Discussion
Subject: RE: Comm Trace



Heh...  I've done that too.  Spend an hour once trying to figure out why
all my SSL data keeps showing up as garbage in communication traces.
Tried different programs.   Even wrote a quick program of my own... Just
couldn't figure it out.

Finally, I smacked myself on the forehead and said "BECAUSE IT'S
ENCRYPTED"


On Fri, 19 Sep 2003, Ian Patterson wrote:
>
> However I tried using it last week to debug a TCP/IP session that was
> transitting SSL data and the trace data was garbage.
> I quite expected that, but I am interested if it can be done, maybe I have
> the wrong settings.
>
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.