Delivery-Date: Wed, 01 Oct 2014 15:51:10 -0400
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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD 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 149651E052B;
	Wed,  1 Oct 2014 15:51:09 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B67072DC3D;
	Wed,  1 Oct 2014 19:50:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 49D482B595
 for <tor-talk@lists.torproject.org>; Wed,  1 Oct 2014 19:50:56 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 8ca-OBy0p5XD for <tor-talk@lists.torproject.org>;
 Wed,  1 Oct 2014 19:50:56 +0000 (UTC)
Received: from atl4mhob07.myregisteredsite.com
 (atl4mhob07.myregisteredsite.com [209.17.115.45])
 by eugeni.torproject.org (Postfix) with ESMTP id 1F09126369
 for <tor-talk@lists.torproject.org>; Wed,  1 Oct 2014 19:50:56 +0000 (UTC)
Received: from mailpod.hostingplatform.com ([10.30.71.211])
 by atl4mhob07.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id
 s91JorW6008111
 for <tor-talk@lists.torproject.org>; Wed, 1 Oct 2014 15:50:53 -0400
Received: (qmail 4773 invoked by uid 0); 1 Oct 2014 19:50:53 -0000
X-TCPREMOTEIP: 162.17.205.153
X-Authenticated-UID: datzrott@alizeepathology.com
Received: from unknown (HELO ALPATH26)
 (datzrott@alizeepathology.com@162.17.205.153)
 by 0 with ESMTPA; 1 Oct 2014 19:50:52 -0000
From: "Derric Atzrott" <datzrott@alizeepathology.com>
To: <tor-talk@lists.torproject.org>
References: <006e01cfdd7f$9fa4b370$deee1a50$@alizeepathology.com>
 <542C2D15.2020101@riseup.net>
 <012401cfdda3$01978a30$04c69e90$@alizeepathology.com>
 <012601cfdda7$67c319b0$37494d10$@alizeepathology.com>
 <CAJoS0DX-7XCY4E=DGuUuptwJFmB_VG1eVJv3pDJ-z5tNvBAMaA@mail.gmail.com>
In-Reply-To: <CAJoS0DX-7XCY4E=DGuUuptwJFmB_VG1eVJv3pDJ-z5tNvBAMaA@mail.gmail.com>
Date: Wed, 1 Oct 2014 15:50:52 -0400
Organization: Alizee Pathology LLC.
Message-ID: <013201cfddb1$020a19c0$061e4d40$@alizeepathology.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH3Ic0CFjPy8W89qtGxwDKfI6rplgJnxOh9AkYCeUgBHWuqqgGv6kARm5FEYAA=
Content-Language: en-gb
Subject: Re: [tor-talk] Wikimedia and Tor
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>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> this is extremely interesting--thank you! but would this work for Tor,
> since presumably the IPs that are blocked are those of the exit relays?
> 
> I am proposing keeping the IPs blocked but opening them up for certain
> logged-in accounts--I don't know if that is technically possible, but it
> seems like a narrower solution, and also theoretically less open to
> abuse/spoofing than unblocking entire IP addresses. (maybe.)

I think you may have misunderstood.  An IP Block Exemption is a flag
applied to a specific account that allows it to ignore IP blocks.

There are two types of blocks that we use for IP addresses, hard blocks
and soft blocks.  A hard block means that if you are using that IP address
you cannot edit Wikipedia.  A soft block means that if you are using that
IP address, you can edit Wikipedia, but only if logged in, and you cannot
make an account.  Many highschools are soft-blocked.  All of Tor is hard-
blocked.  Having the IPBE flag on your account allows you to treat all
hard-blocks as though they are soft-blocks.

Did that explain it any better?

Thank you,
Derric Atzrott
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFULFsORHoDdZBwKDgRAhRPAJ4q+f6M9/KkZ1YvRjJ8hVXJI/a3QACeNCI6
13cqgBU6HIW2jwrKNTti0Yk=
=PMxs
-----END PGP SIGNATURE-----

-- 
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

