From: Richard Stallman <rms@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs/Mutt and Efail or OpenPGP is safer than S/MIME?
Date: Mon, 21 May 2018 00:15:45 -0400 [thread overview]
Message-ID: <E1fKcEb-0007fw-Mc@fencepost.gnu.org> (raw)
In-Reply-To: <87h8n2w7tk.fsf@mat.ucm.es> (message from Uwe Brauer on Sun, 20 May 2018 19:33:27 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>> (setq gnus-blocked-images nil)
> All I can say: I set the variable to nil, I use chrome with the tracker
> email extension, send a message to myself, opening it with emacs/gnus
> and the chrome extension software tells me that I have opened it.
> If the variable is set as it should be, the tracking software does not
> detect that I have opened it.
Thank you. Your evidence shows that this DOES create a vulnerability.
Someone reported adding an explanation of this to the doc string of
gnus-blocked-images. Does it warn about the vulnerability adequately now?
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.
next prev parent reply other threads:[~2018-05-21 4:15 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 8:44 Emacs/Mutt and Efail or OpenPGP is safer than S/MIME? Uwe Brauer
2018-05-15 9:42 ` Lars Ingebrigtsen
2018-05-15 19:26 ` Uwe Brauer
2018-05-15 21:48 ` Lars Ingebrigtsen
2018-05-16 8:22 ` Uwe Brauer
2018-05-16 9:31 ` Lars Ingebrigtsen
2018-05-16 9:56 ` Lars Ingebrigtsen
2018-05-16 8:43 ` Uwe Brauer
2018-05-16 9:32 ` Lars Ingebrigtsen
2018-05-16 10:24 ` Uwe Brauer
2018-05-16 10:30 ` Lars Ingebrigtsen
2018-05-16 2:52 ` Richard Stallman
2018-05-16 8:24 ` Uwe Brauer
2018-05-16 9:30 ` Lars Ingebrigtsen
2018-05-17 3:03 ` Richard Stallman
2018-05-17 7:16 ` Robert Pluim
2018-05-16 15:56 ` Eli Zaretskii
2018-05-16 17:15 ` Andreas Schwab
2018-05-16 17:38 ` Eli Zaretskii
2018-05-16 18:58 ` Andreas Schwab
2018-05-18 2:30 ` Richard Stallman
2018-05-18 12:37 ` Uwe Brauer
2018-05-18 14:05 ` Lars Ingebrigtsen
2018-05-19 8:29 ` Uwe Brauer
2018-05-19 9:59 ` Eli Zaretskii
2018-05-19 10:08 ` Uwe Brauer
2018-05-19 10:12 ` Lars Ingebrigtsen
2018-05-20 3:15 ` Richard Stallman
2018-05-20 3:15 ` Richard Stallman
2018-05-20 17:33 ` Uwe Brauer
2018-05-21 4:15 ` Richard Stallman [this message]
2018-05-20 17:34 ` Lars Ingebrigtsen
2018-05-21 4:15 ` Richard Stallman
2018-07-22 13:58 ` Lars Ingebrigtsen
2018-05-16 19:52 ` Joost Kremers
2018-05-17 3:05 ` Richard Stallman
2018-05-17 3:05 ` Richard Stallman
2018-05-17 15:09 ` Eli Zaretskii
2018-05-18 2:34 ` Richard Stallman
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=E1fKcEb-0007fw-Mc@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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).