Delivery-Date: Mon, 01 Jun 2015 05:31:07 -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,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 DA5FD1E0240;
	Mon,  1 Jun 2015 05:31:04 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 017E635977;
	Mon,  1 Jun 2015 09:30:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id EEBF03595F
 for <tor-talk@lists.torproject.org>; Mon,  1 Jun 2015 09:30:54 +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 CeK0eMY7_aK3 for <tor-talk@lists.torproject.org>;
 Mon,  1 Jun 2015 09:30:54 +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 C90AD35926
 for <tor-talk@lists.torproject.org>; Mon,  1 Jun 2015 09:30:54 +0000 (UTC)
Received: from berryeater.riseup.net (berryeater-pn.riseup.net [10.0.1.120])
 (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 AE7CC413D4
 for <tor-talk@lists.torproject.org>; Mon,  1 Jun 2015 09:30:51 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1433151051; bh=sFOrG2Wg6LJ80asWl6c2IfVc0vZtVGu2qH2BdeBxN/w=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=FqU7vqhlB8mxu0t3zyvGKn4XdY09/GqV43ZyyDKRsYH6fqEdAZAvMLFQ2KnyXKVt3
 GUiBCM26aPZYn2nZwxjLMucHbtDlMoE6fFIP2FoDoiieAbyEUkN+8CwOclnTR+a4k3
 JtkwZ921DvxaSHxV0jdzAGpLbae+O5LZooeumHUY=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir) with ESMTPSA id CAE4A429E5
Message-ID: <556C2659.4000404@riseup.net>
Date: Mon, 01 Jun 2015 03:31:05 -0600
From: Mirimir <mirimir@riseup.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <64d11c8197cd12abf9764685ff007f67.squirrel@sdfeu.org>
 <556BD46A.9090102@riseup.net>
In-Reply-To: <556BD46A.9090102@riseup.net>
X-Virus-Scanned: clamav-milter 0.98.7 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] Invaded by disconnect.me
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>

On 05/31/2015 09:41 PM, Mirimir wrote:
> On 05/31/2015 08:55 PM, Paul A. Crable wrote:
>> Perhaps someone could help me here.  On version 4.5.1 of the Tor (Firefox)
>> browser, the search field, to the right of the place to enter the URL, now
>> has a symbol on it that is proprietary to disconnect.me.  I have also
>> found that while working on the WWW, from time to time a screen comes up
>> from direct.me asking me to enter search terms and to select the search
>> engine to use.
>>
>> It appears that disconnect.me has hijacked the search field in Foxfile,
>> and also found a way to interpose it's own search screen when URL's cannot
>> be found.  I have done nothing to make this happen, and unfortunately
>> don't know what I can do to make it go away.
>>
>> Can anyone explain why this is happening?
>>
>> Until now the default search engine for Tor was Start Page, but that's
>> gone.  Is Tor no longer using Start Page as the default search engine?
>>
>> I expect this kind of thing with a standard browser, but I thought Tor and
>> Foxfile had pretty well locked things down to prevent this kind of thing
>> happening.
>>
>> Any thoughts?
>>
>> Paul
>>
> 
> At first, I was just going to say that disconnect.me is the default
> search option in Tor Browser 4.5.1. But then I see on the blog:[0]
> 
> | Last comment for the disconnect search add-on on on mozillas
> | add-on pages does not sound good.
> |
> |
> https://addons.mozilla.org/en-us/firefox/addon/disconnect-search/reviews/678756/
> |
> | >This plugin should enhance security, but in fact is doing
> | quite opposite.
> | Disconnect-search is regularly uploading plugin settings and
> | usage data, along with unique user ID, browser Agent string
> | and IP address not only to the developers website, but to
> | third parties as well (amazon servers of unknown account and
> | adobe stats servers).
> |
> | That is confirmed in the discussion about a different bug:
> | https://bugzilla.mozilla.org/show_bug.cgi?id=1166692#c1
> 
> Some clarification would be good.
> 
> [0] https://blog.torproject.org/blog/tor-browser-451-released

Looking in Tor browser 4.5.1, I see that the disconnect search add-on is
not installed. And so there's presumably far less of an issue. I should
have checked before replying.

But official clarification would still be good.
-- 
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

