At 4:18 PM -0500 11/14/2002, Bill Cole wrote: >At 11:01 AM -0700 11/14/02, Warren Michelsen imposed structure on a stream of >electrons, yielding: >> >>Can anyone recommend a good DNSBL for open proxies and such, that >>might catch these, without collateral damage? > >opm.blitzed.org
OK, thanks. Question: they seem to use a different return value than other DNSBLs. They say: In the combined zone (opm.blitzed.org) the A record has an IP address of 127.1.0.x where x is a bitmask of the types of proxy that have been reported to be running on the host. The values of the bitmask are as follows: WinGate 1 Socks 2 HTTP Connect 4 Cisco 8 HTTP Post 16 Bitmask? I'm not sure I understand. Which open proxies should I be concerned about (WinGate, Socks, etc.) from the list above and what values do I place in my blacklist for each, what values are returned for each? If I understand this bitmask thing correctly, then the list items would return values as follows: WinGate 127.1.0.1 (1 bit of the last quad set) Socks 127.1.0.3 (2 bits of the last quad set) HTTP Connect 127.1.0.15 (4 bits of the last quad set) Cisco 127.1.0.255 (all 8 bits of the last quad set) HTTP Post ummm... (Heres where the bitmask thing doesn't seem quite right.) Someone please 'splain "bitmask" to me in this application. ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
