Delivery-Date: Fri, 05 Feb 2016 09:04:49 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 98C131E033A;
	Fri,  5 Feb 2016 09:04:47 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B8AB93968D;
	Fri,  5 Feb 2016 14:04:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2523239581
 for <tor-talk@lists.torproject.org>; Fri,  5 Feb 2016 14:04:38 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 1FN1fCpcAxW5 for <tor-talk@lists.torproject.org>;
 Fri,  5 Feb 2016 14:04:38 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 02FCF39508
 for <tor-talk@lists.torproject.org>; Fri,  5 Feb 2016 14:04:37 +0000 (UTC)
Received: from piha.riseup.net (unknown [10.0.1.163])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 4053D1A28CE
 for <tor-talk@lists.torproject.org>; Fri,  5 Feb 2016 14:04:35 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1454681075; bh=jzgPYuoMLh9/HPNH0MBOqv/k9mDRJqehSs2O7sqdXP4=;
 h=From:Subject:Date:References:In-Reply-To:To:From;
 b=esjc9ElZcl4stdw6SDGXamEzf7GxDup+qnVNPbEsczLI6AovwgJNYr3PwhH12jB8X
 XcYhOCiU/w97o8N7CzyNwDvToouIh3uSsd2ChX+Z7sPcWbuZAM7U6Xue89qsuaje1l
 XzBb/UQs0SvhSDLK3/jBLp8giQGfRvpJRGT6btRo=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: scfith) with ESMTPSA id 130BF1C0489
From: Scfith Rise up <scfith@riseup.net>
Mime-Version: 1.0 (1.0)
Message-Id: <DD9B1122-4B5E-4206-B5C5-1722883675A9@riseup.net>
Date: Fri, 5 Feb 2016 09:04:33 -0500
References: <k8zvpue--3-0@tutanota.com> <56a85c39.6080502@ahmia.fi>
 <DC644F66E44.00000281beatthebastards@inbox.com>
In-Reply-To: <DC644F66E44.00000281beatthebastards@inbox.com>
To: tor-talk@lists.torproject.org
X-Mailer: iPhone Mail (13D15)
X-Virus-Scanned: clamav-milter 0.98.7 at mx1.riseup.net
X-Virus-Status: Clean
Subject: Re: [tor-talk] Warning: 37 new booby trapped onion sites
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Is there anyway to somehow automate the process? (The developer in me coming out)

I ask because this seems like something that you will be doing perpetually. Something like an algorithm that can compare percentage match of heuristics of a database of previous sites marked as fake against all new ones and then giving a trust score? 

I'd be happy to help write something in Python to do this & put on github, assuming I can get a decent sets of sample data to test against. 

Or would putting it out there publically allow those creating the fake sites to up their game and change their tactics. Seems like this will always be a cat & mouse game. 

On Feb 5, 2016, at 3:49 AM, I <beatthebastards@inbox.com> wrote:

>> From: juha.nurmi@ahmia.fi
>> I found over 200 more fake onions and filtered them. I don't like that
>> someone sabotages the onion ecosystem.
>> 
>> -Juha
> 
> Good on you for doing that
> 
> 
> -- 
> tor-talk mailing list - tor-talk@lists.torproject.org
> To unsubscribe or change other settings go to
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

