On Thu, Sep 13, 2007 at 10:57:35AM +0100, Rob Oats wrote: || Despite a promising start and submission of a list of the relevant abusive ip || addresses (by myself) and followup emails they have now missed 2 self || imposed deadlines and are now not communicating at all. This means; || 1. They have no idea what they are doing. or; || 2. They are not interested in fixing the problem. || || Personal thoughts are that we find away to forward requests nowhere or with || warning forward requests to a server providing time in the 18th century or || some other arbitrary time which will get their server admins on their backs.
I'd suggest an offset of something like 42 minutes in the future:
* It's unusable for apointments
* You won't miss the appointment, so it's an annoyance only
* You can't ignore the day (hour) and look at the time (minute) only
* After all, it's the ultimate answer
Call it the attention offset, intended to get the attention of client
operators. Configure through the restrict statement:
restrict <abusive-range> ... attention
attention +2520 # optional offset in seconds, default +2520
If many time server operators set the same offset (suggesting the default
+2520), the cause will become easy to find on the web. Then hopefully,
end users will start complaining and/or at looking to other means of
time synchronisation.
This seems pretty easy to do. I might do it myself, if I find the time.
Ciao. Vincent.
--
Vincent Zweije <[EMAIL PROTECTED]> | "If you're flamed in a group you
<http://www.xs4all.nl/~zweije/> | don't read, does anybody get burnt?"
[Xhost should be taken out and shot] | -- Paul Tomblin on a.s.r.
signature.asc
Description: Digital signature
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
