1995-10-07 - Re: Certificate proposal

Header Data

From: “Perry E. Metzger” <perry@piermont.com>
To: Hal <hfinney@shell.portal.com>
Message Hash: acd70adbf2dc4aa36006a49e54b24e97050515d5b9a4650fafb99e615df58a33
Message ID: <199510071748.NAA09738@frankenstein.piermont.com>
Reply To: <199510060440.VAA23299@jobe.shell.portal.com>
UTC Datetime: 1995-10-07 17:48:21 UTC
Raw Date: Sat, 7 Oct 95 10:48:21 PDT

Raw message

From: "Perry E. Metzger" <perry@piermont.com>
Date: Sat, 7 Oct 95 10:48:21 PDT
To: Hal <hfinney@shell.portal.com>
Subject: Re: Certificate proposal
In-Reply-To: <199510060440.VAA23299@jobe.shell.portal.com>
Message-ID: <199510071748.NAA09738@frankenstein.piermont.com>
MIME-Version: 1.0
Content-Type: text/plain



Hal writes:
> Bob Smart <smart@mel.dit.csiro.au> writes:
> >Consider the IPSEC case. The current situation is:
> 
> >1. We go through some process, let's call it Process A, where we determine
> >   that we want to talk to IP address 192.9.8.7.
> 
> This would be, say, a DNS lookup on www.egghead.com.

Just thought I'd point out that IPSEC isn't in general going to use
host keys. Its designed to be more general, and I hope that it ends up
being used much more like Kerberos -- i.e. well known service keys and
user keys.

Perry





Thread