NODE 7a3698a6Question: Key Distr. in realtimeo applications?
Jonathan Rochkind <jrochkin@cs.oberlin.edu>Thu, 7 Jul 94 18:32:45 PDT
Well, I've gotten a few hundred pages into Applied Crypoto, and am now
educated enough to realize what the things are that I don't know.
One question I have is regarding how protocols for realtime
communications work, like say a encrypted voice conversation.
I know there are such things,such as Clipper, but I assume
Clipper/skipjack is atypical in many ways. But maybe I'm wrong.
Anyhow, I'd guess that in such applications, a random one-time session
key is generated for a symmetric encryption method. Is this correct?
If so, how is this key distributed to both participants? You could use
public-key cryptography in some way to distribute the session key,
similar to what DES does, but then how do you distribute the public
keys so as to avoid a man in the middle attack?
Ideally, you want to pick up your crypto-phone, initiate a call to
another crypto-phone which you've never called before, and which was
possibly manufactured yesterday, and be able to exchange keys with it
in a secure fashion. But I can't think of any way to do this, without
opening yourself up to a man in the middle attack.
How does clipper solve this problem? How do other potential realtime
protocols? Or do they just ignore it, and assume that it's going to be
too hard to do a succesful man-in-the-middle attack quickly enough for
a realtime conversation? That would seem to me to be a dangerous
assumption.
I'd appreciate it if anyone could help me out.
NODE 7bffba65Re: Question: Key Distr. in realtimeo applications?
Ian Farquhar <ifarqhar@laurel.ocs.mq.edu.au>Thu, 7 Jul 94 19:03:08 PDT
>How does clipper solve this problem?
It does not. The Clipper initative (FIPS-185) deals solely with the
specification of a symmetric cipher with escrowed keys. Key exchange
and authentication is outside the scope of the protocol, but most
implementations would probably use something like a D-H key exchange
to do it (remember that a Clipperphone guarantees privacy between yourself
and the person on the other end, but does NOT authenticate them to you
or you to them. Man in the middle attacks are obviously possible,
depending on the key exchange protocol that your Clipperphones employ.)
Ian.
NODE a5204a5dRe: Question: Key Distr. in realtimeo applications?
cort <cort@ecn.purdue.edu>Thu, 7 Jul 94 19:55:45 PDT
> If so, how is this key distributed to both participants?
Find Diffie-Hellman in your Schneier.
D-H is a fundamental (in the sense of foundations) protocol which
transmits information "invisibly" (mathematically speaking).
For related invisibility, read about the Dining Cryptographers.
Cort.
NODE 5d264d1dRe: Question: Key Distr. in realtimeo applications?
Adam Shostack <adam@bwh.harvard.edu>Thu, 7 Jul 94 20:43:12 PDT
Jonathan Rochkind wrote:
| How does clipper solve this problem? How do other potential realtime
Capstone implements Diffie Hillman key exchange, as well as providing
some form of RNG on chip. As others have pointed out, Clipper does
not do key exchange.
Adam
--
Adam Shostack adam@bwh.harvard.edu
Politics. From the greek "poly," meaning many, and ticks, a small,
annoying bloodsucker.