all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: oub@mat.ucm.es, eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs/Mutt and  Efail or OpenPGP is safer than S/MIME?
Date: Thu, 17 May 2018 22:30:04 -0400	[thread overview]
Message-ID: <E1fJV9g-0007tZ-93@fencepost.gnu.org> (raw)
In-Reply-To: <87bmdfo2b5.fsf@igel.home> (message from Andreas Schwab on Wed, 16 May 2018 20:58:22 +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. ]]]

  > There are other elements like style sheets that are needed for rendering
  > the whole message.  The point is that the rendering engine needs to
  > support such security measures in the first place.

Yes, that is right.

Referring to any external elements from HTML in an email
exposes the user to various forms of mistreatment.
Security in an MUA includes protecting the user from all that.

  > > (And private/secret correspondence shouldn't include such external
  > > references in the first place, IMHO.)

  > Sadly, most people don't care enough.

It's often not "people".  Many companies systematically use this
security hole to track users.  I am very glad that nobody can
tell whether I have read a message -- because I do it in Emacs.


-- 
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.




  reply	other threads:[~2018-05-18  2:30 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=E1fJV9g-0007tZ-93@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=oub@mat.ucm.es \
    --cc=schwab@linux-m68k.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.