[ntp:questions] Re: Can you test my server please.
mayer at gis.net
Mon Nov 29 17:41:29 UTC 2004
"Wolfgang S. Rupprecht" <wolfgang+gnus20041124T155740 at dailyplanet.dontspam.wsrcc.com> wrote in message news:<x7fz2ykavr.fsf at bonnet.wsrcc.com>...
> Brad Knowles <brad at stop.mail-abuse.org> writes:
> > So, the pool.ntp.org project needs another way to get these
> > people to stop abusing the servers, and the method being proposed by
> > Simon is that we give them an "obvious" bogus time reference, at which
> > point they hopefully decide that we're not a good time server for them
> > and they go away.
> How about this idea: have each client announce it's name and version
> number in every request packet. Unapproved clients get
> ignored/kod-ed/sent-the-wrong-time. For a client to be approved for
> serving at pools.ntp.org someone at pools.ntp.org needs to audit and
> give their stamp of approval. Obvious crap code gets laughed at.
> Code that later misbehaves even though it looks like it should work
> gets its certification pulled.
> This wont stop someone willfully beating on a pools server with
> homegrown code, but then nothing will. We are talking about udp after
> all. The best pools.ntp.org can do is get the attention of the
> developers up front in a way that the developers can't ignore.
Why do people want to reinvent something that's already in NTP 4?
Just use the authentication scheme to authenticate the clients to
the server just like servers are authenticated to the clients today.
More information about the questions