Delivery-Date: Thu, 19 Feb 2015 10:35:27 -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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY,
	URIBL_BLOCKED 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 707CE1E0AE2
	for <archiver@seul.org>; Thu, 19 Feb 2015 10:35:25 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B3ACB32372;
	Thu, 19 Feb 2015 15:35:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id EF9AC31E22
 for <tor-talk@lists.torproject.org>; Thu, 19 Feb 2015 15:35:16 +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 KevoHqTC8Bnv for <tor-talk@lists.torproject.org>;
 Thu, 19 Feb 2015 15:35:16 +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 CBCCA31D40
 for <tor-talk@lists.torproject.org>; Thu, 19 Feb 2015 15:35:16 +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 1584040066
 for <tor-talk@lists.torproject.org>; Thu, 19 Feb 2015 15:35:14 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1424360114; bh=MzfVr3y3c4K0/o+WaIXRvWRbd8Puub+2kaDVEmBzBCU=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=Bk4RniuuwyVa71xiFOtH3crRUY4WxWKh2mrm+t1VQEaVMKOuhxREOA4nYGI3qu2IV
 6QdhbIA5FbaD3G5PphbSnWUJNizH4XxkJA+xSvFZGPnHcs8mFYIYQWK5cqlnnT5qLF
 ZhYt9w14+H4tvjKHUwBvl996I08UBKbBk7vZMHJo=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: sycamoreone) with ESMTPSA id 64A3243393
Message-ID: <54E6023E.2030607@riseup.net>
Date: Thu, 19 Feb 2015 15:33:18 +0000
From: sycamoreone <sycamoreone@riseup.net>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <ff0969f9d2ea5c294f866c4660ebb309@openmailbox.org>
In-Reply-To: <ff0969f9d2ea5c294f866c4660ebb309@openmailbox.org>
X-Virus-Scanned: clamav-milter 0.98.5 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] Tor over SSH (torsocks) (?)
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>

blobby@openmailbox.org:
> Is torsocks still a safe way to do this?

I can't say anything interesting about torsocks as a program, and am a
happy user. But there are some interesting gotchas, mostly caused by the
convenient but unnecessary *magic* in modern interactive shells.

One example: Type

  $ torsocks git push local_brach:remote_br

into a bash prompt on a stock Debian system (with real branch names and
the name of the remote branch not complete). Then press tab for
auto-completion. The branch name will actually be auto-completed, but
the connection to the repository needed to get the list of branche names
won't use torsocks and Tor.

Die ich rief, die Geister, / Werd' ich nun nicht los.

There are ways to solve such problems though, like `man iptables` and a
lot of free time. Or just using Tails.

I have no idea if similar problems also apply to ssh.

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

