On 16/03/13 00:04, Christian Recktenwald wrote:
On Fri, Mar 15, 2013 at 02:39:17PM -0500, David B Funk wrote:
On Fri, 15 Mar 2013, Christian Recktenwald wrote:
On Fri, Mar 15, 2013 at 10:38:53AM -0500, Dave Funk wrote:
On Fri, 15 Mar 2013, Kevin A. McGrail wrote:
On 3/15/2013 9:17 AM, Tom Kinghorn wrote:
On 15/03/2013 15:11, Christopher Nido wrote:
http://www.naturalstonesinc-munged.com/aah/pabfjd/pgrezs
... listing the URLs in some kind of RBL will be probelmatic for FPs.
not really: The part 'aah/pabfjd/pgrezs' is most likely[tm] not
used in normal operation of this site.
The whole raison-detre for RBLs is that they're lists that can be
implemented via the DNS system (created, updated, distributed, queried,
etc).
As such they can -only- contain IP addresses or hostnames, NOT URLs.
that's not exactly right. I've been distributing other data via
DNS for quite some years now like temperature[1], OUIs (mac addresses
prefixes)[2]
and originating time stamps[3] just to name some.
For demonstration purposes please just try:
dig +short txt
http://www.naturalstonesinc-munged.com/aah/pabfjd/pgrezs.url.rbl.citecs.de.
you would get
"1363389581"
which is the epoch timestamp[3] the entry was created.
Why does this work? It's because it uses TXT records, not A or PTR
records. Maybe there would be some funny characters I did not think of
right now - then, some quoting would help.
Creating another rbl providing compromized email addresses would be the
same thing.
The issue isn't A .vs. TXT - it's that certain characters aren't allowed
in DNS names.
Listing e-mail addresses and URL paths could be done by normalizing them
(e.g. lower-case, stripping query parameters etc.) and then hashing them
(e.g. MD5/SHA1 etc) and listing the hash.
As you say though - the issue is collecting the data and populating the
lists along and maintaining the rest of the infrastructure that serves it.
Regards,
Steve.
