Xref: utzoo comp.protocols.kerberos:600 sci.crypt:4238
Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!uunet!shelby!paulf@shasta.Stanford.EDU
From: paulf@shasta.Stanford.EDU (paulf)
Newsgroups: comp.protocols.kerberos,sci.crypt
Subject: Re: timestamp in authentication process
Keywords: authentication protocol, timestamps
Message-ID: <129@shasta.Stanford.EDU>
Date: 28 Feb 91 19:04:55 GMT
References: <9140@star.cs.vu.nl>
Organization: The Three Packeteers
Lines: 11

In article <9140@star.cs.vu.nl> leendert@cs.vu.nl (Leendert van Doorn) writes:
>Its my opinion that this premise is very difficult to fulfill. There are
>two options here: the time server is un-authenticated, or is authenticated.

Actually, not so difficult.  NTP accuracies of milliseconds are common, and
NTP version 2 has a full encyption system for security (although some of the
implementations are weak, leaving the DES keys out in the open) ("Nothing is
so common as the incomplete execution of a Good Idea".).

-=Paul Flaherty, N9FZX      | "Think of it as evolution in action."
->paulf@shasta.Stanford.EDU |       -- Larry Niven and Jerry Pournelle