Delivery-Date: Wed, 18 May 2016 23:09:56 -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,
	FREEMAIL_FROM,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 AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 372271E0BEE;
	Wed, 18 May 2016 23:09:54 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 875D4205F1;
	Thu, 19 May 2016 03:09:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id DDB10205EC
 for <tor-talk@lists.torproject.org>; Thu, 19 May 2016 03:09:44 +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 SY2lBi1rV8NE for <tor-talk@lists.torproject.org>;
 Thu, 19 May 2016 03:09:44 +0000 (UTC)
Received: from forward22m.cmail.yandex.net (forward22m.cmail.yandex.net
 [IPv6:2a02:6b8:b030::16])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id AA766205EB
 for <tor-talk@lists.torproject.org>; Thu, 19 May 2016 03:09:44 +0000 (UTC)
Received: from mxback8m.mail.yandex.net (mxback8m.mail.yandex.net
 [37.140.138.68])
 by forward22m.cmail.yandex.net (Yandex) with ESMTP id 1CAEF21466
 for <tor-talk@lists.torproject.org>; Thu, 19 May 2016 06:09:40 +0300 (MSK)
Received: from web9m.yandex.ru (web9m.yandex.ru [37.140.138.100])
 by mxback8m.mail.yandex.net (nwsmtp/Yandex) with ESMTP id F7VNwWV90A-9dCK8waN; 
 Thu, 19 May 2016 06:09:39 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail;
 t=1463627379; bh=qPouCLQx9c6Rwcs+HbUB9Bg/rs0NQt1uGfp9bZu66z0=;
 h=X-Yandex-Sender-Uid:X-Yandex-Hint:X-Yandex-Hint:From:To:Subject:
 MIME-Version:Message-Id:X-Mailer:Date:Content-Transfer-Encoding:
 Content-Type;
 b=u8PfEn8BmFat3UMmx4c0bczRrutgXotYB8URJkH6YithV+7x9W/gj+94QEIPXCelJ
 cHBzrdy0/RvTtmRNF5WIHtrBG1Q2YLfKMxeh4MqNjcTGMTGlR3UFxa8RHLWWF3X54R
 1ksXUYIN1YE7HquQARRoDTckU2usijcgT26i3skk=
Authentication-Results: mxback8m.mail.yandex.net;
 dkim=pass header.i=@yandex.com
X-Yandex-Suid-Status: 1 0,1 865868569
X-Yandex-Sender-Uid: 324913609
Received: by web9m.yandex.ru with HTTP;
	Thu, 19 May 2016 06:09:39 +0300
From: Cain Ungothep <ungocain@yandex.com>
To: tor-talk@lists.torproject.org
MIME-Version: 1.0
Message-Id: <2091171463627379@web9m.yandex.ru>
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Thu, 19 May 2016 05:09:39 +0200
Subject: Re: [tor-talk] augmented browsing - "sed inside torbrowser"
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>

Using sed/awk/etc. for website transformation sounds very silly.  Your
scripts will turn completely unwieldy as soon as you try to do something
non-trivial.

You can do much more, much easier by using your own self-served javascript.

And you don't need to install extra addons like Greasemonkey for that
(people just shouldn't install anything on top of Tor Browser, unless they
are competent programmers and have audited the code).  Nor enabling
javascript for the website itself.  All you need is already conveniently
packaged in Tor Browser: NoScript.

Learn about NoScript surrogates.

Note: NoScript surrogates are not equivalent Greasemonkey scripts,
feature-wise.

Warning: You have to think carefully about the sort of transformations you
make and in what context you make them.  Because they could be used to
fingerprint you.

PS: Talking about code audits: How many of you have looked at NoScript's
source?  I have.  I was happier prior.
-- 
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

