Delivery-Date: Sun, 20 Sep 2015 12:24:14 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_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 4188D1E0B40;
	Sun, 20 Sep 2015 12:24:12 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6F5F7372FB;
	Sun, 20 Sep 2015 16:24:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 20F3837287
 for <tor-talk@lists.torproject.org>; Sun, 20 Sep 2015 16:24:04 +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 gvn4TyTybkxI for <tor-talk@lists.torproject.org>;
 Sun, 20 Sep 2015 16:24:04 +0000 (UTC)
Received: from mail.bitmessage.ch (mail.bitmessage.ch [146.228.112.252])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id B04D2371BA
 for <tor-talk@lists.torproject.org>; Sun, 20 Sep 2015 16:24:03 +0000 (UTC)
dkim-signature: v=1; a=rsa-sha256; d=bitmessage.ch; s=mail;
 c=relaxed/relaxed; q=dns/txt;
 h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References;
 bh=hmiCFT8sxboEGvC94Aepa/vJIZzDlO0iORTmmaIysrA=;
 b=Yyp7pTD0vZUo9Jhur+ruB+XygzFixCexX3d12ndfVlge8qByOVomfD0AWEU+LoNhp7ul3I7fmtEdt5+TBCd819H0SPn10+nAc3yj2n1wqpqAE75OkLorupWX1Rj8+BZ89MTJEVRNweOyDsvEwBdNTQY1lX/CdTzSZ7MWuXYrWW8=
Received: from 127.0.0.1 (BITMESSAGE [127.0.0.1])
 by mail.bitmessage.ch with ESMTPSA
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128)
 ; Sun, 20 Sep 2015 18:23:23 +0200
Message-ID: <55FEDD8D.6010509@bitmessage.ch>
Date: Sun, 20 Sep 2015 16:23:41 +0000
From: Tempest <tempest@bitmessage.ch>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <55F6100C.5030200@bitmessage.ch>
 <20150916221055.GP5172@patternsinthevoid.net>
In-Reply-To: <20150916221055.GP5172@patternsinthevoid.net>
Subject: Re: [tor-talk] tor + twitter issues
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="windows-1252"
Content-Transfer-Encoding: quoted-printable
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

isis:
> Tempest transcribed 2.4K bytes:
>> twitter's security configuration seems to be at war with tor. had to do
>> multiple resets over past 24 hours, only to see a perpetual "lock" in
>> place recently. i filed a support ticket. here's twitter's response.
> =

> Hey All,
> =

> I was contacted by some nice folks at Twitter who have worked to resolve =
this
> issue.  The problems with Tor users being locked out of their Twittter
> accounts and asked for phone number *should* be fixed, but I wasn't given
> many details as to what the fix entails, so=85
> =

> Is anyone still having troubles which they believe to be caused by using =
Tor?

i'm locked out again. it is also asking me for a phone number again.

twitter's canned response appears to be "we are not going after tor."
yet, oddly enough, all i'm doing is using the tor browser to engage with
the accounts i regularly do over twitter. no posting bots or third party
software is used.

-- =

gpg key - 0x2A49578A7291BB34
fingerprint - 63C4 E106 AC6A 5F2F DDB2 3840 2A49 578A 7291 BB34

-- =

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

