1993-04-19 - How tapper works: see alt.privacy.clipper

Header Data

From: david@staff.udc.upenn.edu (R. David Murray)
To: cypherpunks@toad.com
Message Hash: 2789db1437912af5647ad891ec7850ab53649fa7f26e63844c8e0cf524a89024
Message ID: <9304192001.AA18866@staff.udc.upenn.edu>
Reply To: N/A
UTC Datetime: 1993-04-19 20:03:35 UTC
Raw Date: Mon, 19 Apr 93 13:03:35 PDT

Raw message

From: david@staff.udc.upenn.edu (R. David Murray)
Date: Mon, 19 Apr 93 13:03:35 PDT
To: cypherpunks@toad.com
Subject: How tapper works: see alt.privacy.clipper
Message-ID: <9304192001.AA18866@staff.udc.upenn.edu>
MIME-Version: 1.0
Content-Type: text/plain


If it is not too late, please ignore my previous request for an
explanation of how tapper works.  I found the answer in
alt.privacy.clipper.  The missing piece of info was that the session key
must be negotiated separately.
-- 
david			david@staff.udc.upenn.edu

Thread

• Return to April 1993

• Return to “david@staff.udc.upenn.edu (R. David Murray)”

• 1993-04-19 (Mon, 19 Apr 93 13:03:35 PDT) - How tapper works: see alt.privacy.clipper - david@staff.udc.upenn.edu (R. David Murray)