Delivery-Date: Fri, 20 Nov 2015 18:14:26 -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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	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 ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 80FBD1E0A88;
	Fri, 20 Nov 2015 18:14:24 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 012EA36CA5;
	Fri, 20 Nov 2015 23:14:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D6BBF36BE0
 for <tor-talk@lists.torproject.org>; Fri, 20 Nov 2015 23:14:15 +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 UN6lQZnWPz5Y for <tor-talk@lists.torproject.org>;
 Fri, 20 Nov 2015 23:14:15 +0000 (UTC)
Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com
 [IPv6:2607:f8b0:4002:c07::233])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id A85AD36746
 for <tor-talk@lists.torproject.org>; Fri, 20 Nov 2015 23:14:15 +0000 (UTC)
Received: by ykdr82 with SMTP id r82so181690631ykd.3
 for <tor-talk@lists.torproject.org>; Fri, 20 Nov 2015 15:14:13 -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=gwUd1EOajMJwAGS5sB73M8jTisNC3cIO2kifPfTeL0I=;
 b=bmWLF4o8IZNQRsgyaDjIfkn2OYgI+qbQQZj6NT2FBj+8Mx9+/gA2WvNVnf2ZDod6JJ
 a0BlGf3gMAzgjEfrP5SN5yELJSHoIDorTdlJ1wS+tf50Z6YGTJr9OPpBui9mr8hpR9At
 nE2qpvfhzoci7+ZzfmzP8SzFzdfDsfDKx28c9O7zk28vU8lOZTN+swYdckMBwJZJB9HC
 vzIyWGHg0y7dEcyXqvqsNyEIFlJ30UI9Fhimxx177K7cN8LRIK5xAWC6h9h//cVH2jkZ
 A/JH4AQc2yhVsusS/2bmV7PdFLgVb2DA+wwajNZ/ySXrIC5XZO2AvkFb+eWAd6AHXBAW
 wFmg==
MIME-Version: 1.0
X-Received: by 10.129.156.88 with SMTP id t85mr17412121ywg.156.1448061253072; 
 Fri, 20 Nov 2015 15:14:13 -0800 (PST)
Received: by 10.129.74.4 with HTTP; Fri, 20 Nov 2015 15:14:13 -0800 (PST)
Date: Fri, 20 Nov 2015 18:14:13 -0500
Message-ID: <CAB7TAMks0Ynrfm_8-0RXb0SME3DR63auqNEgv2Tzd_VopM5H1A@mail.gmail.com>
From: Allen <allenpmd@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] MITM attack on TLS
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>

If your IT department allows outgoing SSH, then spin up a micro Linux EC2
instance on Amazon Web Services (which costs only 1.3 cents per hour), then
SSH into the EC2 instance and setup an SSH tunnel.

Assuming your local machine is running Windows, you can use Putty as the
SSH client.  If you just want to use the EC2 instance as a proxy (without
Tor), then in the  Putty configuration, look under Connection -> SSH ->
Tunnels, for Source port pick any high number like 9000, pick Dynamic,
click Add, then Open the session, finally, configure your browser to
connect to a SOCKS4 proxy on 127.0.0.1 at the port you chose (like 9000).

If you want to use Tor, too, then download and start torproxy on the EC2
instance.  Assuming the torpoxy port on the EC2 instance is 9050, then in
the Putty configuration under Connection -> SSH -> Tunnels, for Souce port
pick any high number like 9000, pick Local and in the Destination field
enter 127.0.0.1:9050, click Add, then Open the session and again configure
your browser to connect to a SOCKS4 proxy on localhost at the port you
chose (like 9000).

If you've never used EC2 before, it will probably take you 1-2 hours to do
this the first time (maybe you can find a tutorial on the www or
something), but once you get it set up it works quite nicely, and the price
is right.
-- 
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

