unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Max Zettlmeißl" <max@zettlmeissl.de>
To: emacs-devel@gnu.org
Subject: Re: flag to use tor
Date: Tue, 17 Nov 2020 07:31:20 +0100	[thread overview]
Message-ID: <CAB+SxbyBJE0rsSAifXNiR7EdWw+4=JgfSm4ZR_sLOAeUo8GNeQ@mail.gmail.com> (raw)
In-Reply-To: <E1ketIz-0008Np-C3@fencepost.gnu.org>

On Tue, Nov 17, 2020 at 6:14 AM Richard Stallman <rms@gnu.org> wrote:
> I want to connect through Tor all the time, but sometimes these
> commands betray me.  I added a switch to VC to make it connect
> through Tor always, but it would be good to have a facility that
> would do this to all internet connections that Emacs packages make.
>
> Some packages connect directly in Lisp. and some connect by running
> subprocesses.  For the subprocesses, using 'torsocks' is an easy fix.
> The hard part is to change all the packages that need fixing.

I have been missing such a feature too.
The hardest part when not routing every single connection through Tor
on a lower level, is to know whether all connections originating from
Emacs really are going through Tor and I have always been hesitant to
fully trust the solutions which I came up with.
The solution which I trusted most, was running Emacs in a separate
network namespace and routing all the namespace's connections through
Tor.

> A super-simple approach is to have a switch with two settings: Tor, or
> not Tor.  A more complex feature would give a systematic way to
> specify exceptions.

I guess a more fine grained approach is required to really provide a
solution to everyone.
One example of a case where one might desire a more fine grained
control: When using tramp mode to edit files on a server, one might
not always be in a position where a connection from a Tor node is
allowed by the server.

I'm in favour of such a facility, but it should not provide a false
sense of security and therefore in my opinion either be implemented
properly or not at all.



  parent reply	other threads:[~2020-11-17  6:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  5:13 flag to use tor Richard Stallman
2020-11-17  5:30 ` Jean Louis
2020-11-17  6:31 ` Max Zettlmeißl [this message]
2020-11-17  7:59 ` Colin Baxter
2020-11-17  8:34   ` Colin Baxter
2020-11-17 12:43 ` Zhu Zihao
2020-11-21  5:04   ` Richard Stallman
2020-11-23  9:33     ` Robert Pluim
2020-11-24  5:53       ` Richard Stallman
2020-11-22 16:01   ` Tomas Hlavaty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAB+SxbyBJE0rsSAifXNiR7EdWw+4=JgfSm4ZR_sLOAeUo8GNeQ@mail.gmail.com' \
    --to=max@zettlmeissl.de \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).