1995-08-04 - Re: SSLeay - Whats the story…

Header Data

From: Alex Tang <altitude@cic.net>
To: enzo@ima.com (Enzo Michelangeli)
Message Hash: 8c2ecb7c17c9e736fb38bccd56c9bf19440a33c412cd699755844bd90b50f47a
Message ID: <199508040455.AAA18486@petrified.cic.net>
Reply To: <Pine.LNX.3.91.950804104356.9665A-100000@ima.net>
UTC Datetime: 1995-08-04 04:55:54 UTC
Raw Date: Thu, 3 Aug 95 21:55:54 PDT

Raw message

From: Alex Tang <altitude@cic.net>
Date: Thu, 3 Aug 95 21:55:54 PDT
To: enzo@ima.com (Enzo Michelangeli)
Subject: Re: SSLeay - Whats the story...
In-Reply-To: <Pine.LNX.3.91.950804104356.9665A-100000@ima.net>
Message-ID: <199508040455.AAA18486@petrified.cic.net>
MIME-Version: 1.0
Content-Type: text/plain


On Thu Aug  3 23:45:04 1995: you scribbled...
> 
> On Thu, 3 Aug 1995, Jason Weisberger wrote:
> 
> > Maybe I miss it, but when did this arrive?  Is anyone testing it?
> 
> You may take a look at http://www.psy.uq.oz.au/~ftp/Crypto/
> 
> My initial enthusiasm has somewhat vanished when I've realized that a 
> free SSL implementation doesn't automatically allow to build a 
> Netsite-compatible server: without a certificate issued by Verisign on 
> behalf of Netscape Communications, Netscape Navigator won't talk to it.
> As SSL has some intrinsic points of weakness, I don't see the point
> of sticking to it to secure the TCP layer.

just wondering but...What are the intrinsic points of weakness?  

...alex...




Thread