unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, "'Eli Zaretskii'" <eliz@gnu.org>
Subject: Re: Recent fix in handling vc-tor
Date: Thu, 22 Sep 2022 12:51:59 +0200	[thread overview]
Message-ID: <87tu4z7kc0.fsf@gnus.org> (raw)
In-Reply-To: <E1obCdz-0003dC-FU@fencepost.gnu.org> (Richard Stallman's message of "Wed, 21 Sep 2022 23:12:55 -0400")

Richard Stallman <rms@gnu.org> writes:

> The bug that made setting vc-tor a no-op was particularly treacherous.
> since the feature led people to believe they got some protection
> for their privacy, but it didn';t actually work.
>
> I think we should release a 28.3 with this change, and fairly soon,
> even if no other changes are needed.

vc-tor is for using VC commands via Tor?

Emacs does not, in general, work well with Tor -- Emacs leaks all over
the place (especially w.r.t. DNS lookups), so somebody trying to retain
full privacy by setting that variable will probably be found out anyway.

But it does seem like a pretty bad problem, even if I expect that
virtually nobody is using vc-tor, so perhaps we should do an Emacs 28.3
release.  I'm not at all sure, though.  Eli, what do you think?




  reply	other threads:[~2022-09-22 10:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  3:12 Recent fix in handling vc-tor Richard Stallman
2022-09-22 10:51 ` Lars Ingebrigtsen [this message]
2022-09-22 10:59   ` Lars Ingebrigtsen
2022-09-23  3:16     ` Richard Stallman
2022-09-22 11:17   ` Philip Kaludercic
2022-09-22 11:42     ` Stefan Kangas
2022-09-23  3:16       ` Richard Stallman
2022-09-23  8:34         ` Robert Pluim
2022-09-22 12:32   ` Eli Zaretskii

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=87tu4z7kc0.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).