Delivery-Date: Tue, 20 Jan 2015 00:13:36 -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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,
	URIBL_BLOCKED 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 135C01E0BF8
	for <archiver@seul.org>; Tue, 20 Jan 2015 00:13:35 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 5502832E34;
	Tue, 20 Jan 2015 05:13:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A27ED32E48
 for <tor-talk@lists.torproject.org>; Tue, 20 Jan 2015 05:13:27 +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 ZSLZZ2cD95wo for <tor-talk@lists.torproject.org>;
 Tue, 20 Jan 2015 05:13:27 +0000 (UTC)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com
 [IPv6:2a00:1450:400c:c00::22f])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 532F63285E
 for <tor-talk@lists.torproject.org>; Tue, 20 Jan 2015 05:13:27 +0000 (UTC)
Received: by mail-wg0-f47.google.com with SMTP id n12so5049440wgh.6
 for <tor-talk@lists.torproject.org>; Mon, 19 Jan 2015 21:13:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=2sZAxV9aPvCgj6yyu8TRP0CzwaI1O+i656xwo84Un3Q=;
 b=ohG8slk89ut/FpajzCxg60zevDU84V6Oj3pE/GMSDp2D1ElaxluU2hChGKQnHdt7hl
 gzRaLeKrMAZcpke/yq+bg+mKPXXpJ+OioIst4gJMjR3Eyn9ZCaBcp1FF3Od+MgeiRn3K
 k/Am7B196wFs5pVQyUWosBvb34Oxd8U63ZIDzTyrYzhWV+LhJ0EYPA6lD9rOdpBSkacG
 yTwKIs9RY69Ht/6CtJ3kSCpsge48WBbPYH1iR5mCuyzyhlkF+DMr5znsui/X7PoIfjnf
 xRRHPdi6hLbwX27kv392vHuj1NhzjD26+Nb1UpHYOrYAsZVChVzF8cwKibFitmLs42DQ
 2cLg==
MIME-Version: 1.0
X-Received: by 10.180.231.33 with SMTP id td1mr41663128wic.33.1421730804473;
 Mon, 19 Jan 2015 21:13:24 -0800 (PST)
Received: by 10.216.106.136 with HTTP; Mon, 19 Jan 2015 21:13:24 -0800 (PST)
Date: Tue, 20 Jan 2015 00:13:24 -0500
Message-ID: <CAD2Ti2-Jb4SJ7v+A_L9As5-x=H8oK4nBHG5mghkZqD5eBQybSA@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: [tor-talk] Craigslist now blocking all Tor IPs? Template for anyone:
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>

> This IP has been automatically blocked.
> If you have questions, please email:
> blocks-b1417151083131383@craigslist.org

minor update while looking at some popular
sites...

Considering this one encodes epoch time of
block in first ten digits, one could discern
some policy by parsing the string each
exit sees to find blocking time distribution.
For instance this one seems long 53 days.
Maybe multiple same epoch or last part of
strings will be found repeated across exits
as if part of an event. Leading key letter and last
7 digits (3 which maybe millisecond) may also become
clearer. No, I never heard back from various questions
made as clearly invited to do above. Shame.
They make hard for people to patronize their site, o well.
-- 
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

