-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I know that pool.ntp.org is probably in a different class than IRC servers/users, but here is a problem we had with IRC server pools.
Back when I ran an IRC network we had "us.example.com" as well as specific hostnames like "kechara.example.com" for users to connect to. Any server that was accepted as part of the network had to have certain things available, specifically a set of TCP ports that connected to it. To be in the pool, other restrictions and commitments were necessary. One BIG problem we had was that some servers also listened on TCP ports and served data from those that were unwanted by our network. To make matters worse, often time IRC hosting sites were on shared computers, and the admin of those computers would suddenly decide to run a porn redirect site on port 80. I'm sure they make a lot of money that way. I'd not be too shocked to run through the ntp pool servers and find a few of these as well. I don't know what sort of restriction I'd want to place on what can be served from port 80, but I know I'd be pretty shocked if I went to http://pool.ntp.org and saw a penis. Not because the penis is shocking (although it could be) but because a penis has little to do with NTP. - --Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGbcKyuzMQWQwZDN0RAvTMAJwImdvSu09aN3So4FmnKfhU5qYRaQCcCRbS 5uBxFqwPcDfg18McloTJhSY= =rCny -----END PGP SIGNATURE----- _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
