all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: Emacs/Mutt and  Efail or OpenPGP is safer than S/MIME?
Date: Fri, 18 May 2018 14:37:50 +0200	[thread overview]
Message-ID: <87vabl5ech.fsf@mat.ucm.es> (raw)
In-Reply-To: E1fJV9g-0007tZ-93@fencepost.gnu.org

[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]


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


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



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

A word of warning should be added.

There are configuration in emacs, for which  such a tracking is
successful.

For example using gnus the setting

(setq gnus-blocked-images nil)



Explanation.

I was not aware of this sort of tracking software and found out that
google's chrome browser has dozen of extension for email tracking, some
of them commercial. I downloaded and tried all of them, (well the ones
which did not require a payment). I then sent message to my own account
(my university switched to a google account which I access via imap).

Indeed with the above setting one extension successfully discovered that
I read an email with gnus/emacs.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]

  reply	other threads:[~2018-05-18 12:37 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 [this message]
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=87vabl5ech.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --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 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.