1996-08-13 - Re: (Off Topic) Re: FCC_ups

Header Data

From: daw@cs.berkeley.edu (David Wagner)
To: cypherpunks@toad.com
Message Hash: a0dca4220ce6ca763a6a2b1a53d1d85e9c38ba5c8cb7a1104b9041b946c22e23
Message ID: <4upjp5$tc@joseph.cs.berkeley.edu>
Reply To: <199608120538.WAA29683@dns2.noc.best.net>
UTC Datetime: 1996-08-13 13:30:32 UTC
Raw Date: Tue, 13 Aug 1996 21:30:32 +0800

Raw message

From: daw@cs.berkeley.edu (David Wagner)
Date: Tue, 13 Aug 1996 21:30:32 +0800
To: cypherpunks@toad.com
Subject: Re: (Off Topic) Re: FCC_ups
In-Reply-To: <199608120538.WAA29683@dns2.noc.best.net>
Message-ID: <4upjp5$tc@joseph.cs.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain


In article <Pine.BSF.3.91.960812153240.26183B-100000@mcfeely.bsfs.org>,
Rabid Wombat  <wombat@mcfeely.bsfs.org> wrote:
> ob crypto (for anyone who read this far): When packet switched voice 
> systems become a reality, how can secure calls be placed to any number? 
> Key exchange during call set-up? How long will this make the call set-up?

This is easy.  Just use end-to-end encryption.  No sweat.  (So what if
call setup takes a half a second to do a public key encryption?  The phone
rings for a couple of seconds before the other guy picks it up anyhow.)

Well, there's that nasty key distribution and management problem (e.g.
who certifies the millions of public keys corresponding to everyone's
phone number?), but that's not specific to voice traffic, and this is
a well-known annoying problem.


The *real* challenge: how do you support sender- and recipient- anonymous
phone calls with strong security?  Have fun.





Thread