[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#366482: marked as done (ITP: dnscruft -- feeds Bind a list of domains as useful as doubleclick.com or less)

Your message dated Sun, 24 Jun 2007 11:59:32 -0600
with message-id <E1I2WN2-0006a1-5H@merkel.debian.org>
and subject line WNPP bug closing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Adam Borowski <kilobyte@mimuw.edu.pl>

* Package name     : dnscruft
  Version          : 0.20060508-1
* URL              : file://home/kilobyte/dnscruft/
  Initial packages : http://angband.pl/debian/dnscruft/
  Apt              : deb[-src] http://angband.pl/debian unstable main
* License          : GPL
  Description      : feeds Bind a list of domains as useful as doubleclick.com or less
 Adverts are an atrocity that plagues "teh Intarweb"; in a typical ISP
 scenario you can expect even up to 1/3 of all http requests to carry
 annoyances instead of useful traffic.  Moreover, such requests are
 usually not-cacheable.
 .
 This package can seed up your DNS server with either prepackaged lists of
 domains or your own selection; it may be used to fight ads/crapware or to
 help enforce your policy against any list of sites you have a database of.
 .
 For the purpose of blocking ads you may want to also look at an alternate
 means like FireFox+Adblock for personal use or Squid+Adzapper for your
 users -- these means grant a more fine-grained control.  On the other
 hand, dnscruft uses far less resources and blocks a much greater range
 of win32 malware, browser hijackers, drive-by-downloads, traffic analysis
 spies or fine products of Russian newest phisheries.
 And, no one says you can't use both dnscruft and URL-based controls.


Annoyed by the amount of crap, I've taken my personal block lists
(gathered over a few years) and combined them with a number of publicly
available ones.  However, the lists I found all contain quite a lot of
false positives -- domains which contain not only cruft but also some
(questionably) redeeming values.  Popular items include for example
rackspace.com (Fanatical Ads(tm)), eads.com (aeronautics),
astalavista.box.sk (a search engine for cracks/serials) or even
myspace.com (THE bane of good taste/reason).  Thus, such existing
lists may be used as-is only on personal/company networks.

To make them useful, I've included only entries I've checked by hand.
As checking >120000 hosts would be an inhuman task, I covered only
those with most incidence on the source lists and/or in Squid logs of
two ISPs which are ahead of others in my quest for world domination.
Thus, I believe a good percentage of current scum will be blocked
with very few false positives.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

--- End Message ---
--- Begin Message --- 
Hello,

This is an automatic mail sent to close the ITP you have reported or 
are involved with.

Your ITP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.

As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not 
intended by owners and submitters (like you) to be closed, for
example if the ITP is still of your interest, or there has been 
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail control@bugs.debian.org
with a body text like this:

 reopen 366482
 stop

Further comments on the work done in the bug sent to
366482@bugs.debian.org would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <damog@debian.org>.

A similar process is being applied to other kind of wnpp bugs.

Thanks for your cooperation,

 -- David Moreno Garza <damog@debian.org>.

--- End Message ---
Reply to: