On Thu, 14 Jun 2007, Ask Bjørn Hansen wrote:
Uh - obviously I wasn't clear - my apologies!
I'm just planning the monitoring to be an encouragement to setup the
redirects and (later) to keep track of what content is being served. How
exactly it should work I'm not sure about. My main concern is people trying
to redirect the traffic to inappropriate content for profit.
Also, the monitoring could be close to useless against organized groups or
at least it could become a cat and mouse game. People going to the trouble
of intentionally serving bad content might go to the trouble of sending
the right content ONLY to the monitoring tool IPs while diverting other
users towards their preffered target site.
It is really trivial to do this in apache.
Really pushing that principle, I could setup my pool server to return the
right time to the pool monitoring tool while diverting all other traffic
to a ntp server returning bogus time. I do not see which gains I would
get from doing that although.
I don't know how likely it is that somebody actually does this for the
http port although. But since it could possibly generate profits, it is
at least possible that this could happen some day.
And against skilled people, it could be hard to monitor the content
that some users "really see". You would have to conneci to such
server from virtually all subnets (well, in theory every IP) in the world
to make sure ;-)
It is just like redirecting to a different local site depending on the
client GeoIp location. So nothing new here, simple client IP to service
mapping like it's already done in many setups.
-Louis
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
