1995-09-02 - Re: SSL attack

Header Data

From: don@cs.byu.edu
To: cypherpunks@toad.com
Message Hash: 5f7ec2315ed8230bf32af9b523082a0f6c91515d69192758cbb0c84381d31d9c
Message ID: <199509020358.VAA00340@wero>
Reply To: N/A
UTC Datetime: 1995-09-02 04:58:01 UTC
Raw Date: Fri, 1 Sep 95 21:58:01 PDT

Raw message

From: don@cs.byu.edu
Date: Fri, 1 Sep 95 21:58:01 PDT
To: cypherpunks@toad.com
Subject: Re: SSL attack
Message-ID: <199509020358.VAA00340@wero>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

From: "Robert A. Rosenberg" <hal9001@panix.com>

>I thought that the ACK gives starting location and number of segments. If I
>get 500 segments and ACK at the 50% point I am sending an ACK for the
>Starting Point and 250 Segments (the unprocessed part would then ACK

With multiple heirchical servers, you don't have the same bottleneck 
problems. If you have a random mode that you can switch into, same deal
(if you care to use it). There are a lot of people who want the anonymity
and server-independance of random mode. There are people who don't want
to add another 37% onto the processing time, given the unlikeliness of
a D.O.S. attack on the server. I continue to support the idea of a 
two-pronged attack using both methods.

Given that most of the server bottleneck was un-updated clients anyway,
I think that the bottleneck-on-the-server problem is solved anyway, 
meaning there won't be any problems getting new keys - thus eliminating
the need for a keyspace buffer queue.

Don

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQB1AwUBMEfVssLa+QKZS485AQEV9QMAoue7RyySe1H0a7s6hBkjf7knaXesLY1h
ZQg9rBZ9ZieJ5qWyBHL03Gn4XikSD8U6/MBbiyMvOnz+QTYRQcMxQioEu4YDcFdD
etaful6wYhtXzd/MTn+VWjBf86poDeNK
=Mp2o
-----END PGP SIGNATURE-----
<don@cs.byu.edu>           fRee cRyPTo!   jOin the hUnt or BE tHe PrEY
PGP key - http://bert.cs.byu.edu/~don     or PubKey servers (0x994b8f39)
  June 7&14, 1995: 1st amendment repealed.  Death threats ALWAYS pgp signed
* This user insured by the Smith, Wesson, & Zimmermann insurance company *





Thread