bugtraq - Re: On-going Internet Emergency and Domain Names

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <TheMailAgent.146589929895e6a@1eee107673eb7786db02e>
Date: Sun, 8 Apr 2007 09:39:48 +0300 (IDT)
From: Alexander Klimov <alserkli@...ox.ru>
To: bugtraq@...urityfocus.com
Subject: Re: On-going Internet Emergency and Domain Names

On Mon, 2 Apr 2007, Bob Fiero wrote:
> RBLs such as SpamCop gave me an idea a few years back. We should
> build a virtual wall around the country.

In theory it is a good idea, but in practice it is not clear if
the rate of false positives or false negatives will not ruin the
system. Even if you propose to use it only against malware, it
can be the case that a server is hosted on an 0wned ADSL host
with dynamic IP. You decide to block the whole subnet of the
ISP -- now all the ISP customers are in trouble.

Aside from technical problems there are also possibility for
misuse both from insiders and outsiders. Now you don't need
a DDoS to bring competitor's site down: just pay insider to
include the site into the block list or put something that can
be mistaken for malware in some obscure "user comments" section
of the target site.

Once the system is in place, it will be used to block other
types of "bad" sites as well. Of course, nobody wants to make
a public directory of "bad" sites, so there will be no easy way
to know what is blocked. See <http://ice.citizenlab.org/?p=260>
for discussion of the mission creep in such systems.

-- 
Regards,
ASK