Article View: sci.crypt
Article #2754Re: Anti-spoofing protocol?
From: Phil Karn
Date: Tue, 05 Jan 1993 03:18
Date: Tue, 05 Jan 1993 03:18
15 lines
1310 bytes
1310 bytes
In article <1993Jan4.215027.17258@netcom.com> rcain@netcom.com (Robert Cain) writes: >This all assumes that you have a secure means of getting your public key >to the other or an authenticated one. Both seem equivalent in the end >to swapping a secret key to me. This makes me question the fundamentals >of PK actually. Why do you say that? An authenticated channel is much easier to get than an authenticated and secret channel. I can get pretty good authentication right now by calling up somebody on the phone whose voice I know well and exchanging MD5 hashes of whatever information we want to authenticate (e.g., a public key). I could care less if somebody eavesdrops this call, but I certainly *would* care if we were exchanging secret DES keys instead. Phil
Technical Details
Message-ID:
<1993Jan5.031805.26623@qualcomm.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!sdd.hp.com!spool.mu.edu!wupost!emory!swrinde!network.ucsd.edu!qualcom.qualcomm.com!servo.qualcomm.com!karnReferences:
<1993Jan4.104051.23477@qualcomm.com> <1993Jan4.215027.17258@netcom.com>Show Full Headers
Complete Article Headers
Newsgroups: sci.crypt Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!sdd.hp.com!spool.mu.edu!wupost!emory!swrinde!network.ucsd.edu!qualcom.qualcomm.com!servo.qualcomm.com!karn From: karn@servo.qualcomm.com (Phil Karn) Subject: Re: Anti-spoofing protocol? Message-ID: <1993Jan5.031805.26623@qualcomm.com> Sender: news@qualcomm.com Nntp-Posting-Host: servo.qualcomm.com Organization: Qualcomm, Inc References: <1993Jan4.104051.23477@qualcomm.com> <1993Jan4.215027.17258@netcom.com> Date: Tue, 5 Jan 1993 03:18:05 GMT Lines: 15