unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Richard Stallman <rms@gnu.org>
Cc: larsi@gnus.org, 24489@debbugs.gnu.org
Subject: bug#24489: efaq: security risks
Date: Fri, 23 Sep 2016 22:45:59 -0400	[thread overview]
Message-ID: <87intmypzs.fsf@lifelogs.com> (raw)
In-Reply-To: <E1bnXFI-0005ex-Io@fencepost.gnu.org> (Richard Stallman's message of "Fri, 23 Sep 2016 16:38:56 -0400")

On Fri, 23 Sep 2016 16:38:56 -0400 Richard Stallman <rms@gnu.org> wrote: 

RS> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
RS> [[[ whether defending the US Constitution against all enemies,     ]]]
RS> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]

>> Images and other resources can carry constructed data and be used as an
>> execution backdoor through browser or library bugs. The following don't
>> necessarily apply to Emacs, they are just examples of the variety and
>> severity of these attacks, which have risen in popularity as direct code
>> injection has become harder:

RS> It is no use telling people, "Be afraid of browsing."

The original suggestion by Glenn was to say that remote HTML content is
a potential security risk. That's a statement of fact and I gave
supporting evidence. Those risks apply to Emacs users, but I don't think
anyone proposed "be afraid" to be the message we should give.

RS> If we can't give any advice more specific than that, it would
RS> be a useless annoyance.

Certainly. The FAQ can link to external resources, for instance. I think
in the FAQ we should at least list the libraries that Emacs uses to
render remote content (SVG, XML, PNG, etc.) so the user is aware of
those dependencies and will keep them up to date.

But the method for that depends on the platform, so... do we explain in
the FAQ? Does Emacs itself warn when libraries are out of date? I don't
know.

Ted





  reply	other threads:[~2016-09-24  2:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 22:48 bug#24489: efaq: security risks Glenn Morris
2016-09-20 22:53 ` Lars Ingebrigtsen
2016-09-21 21:26 ` Richard Stallman
2016-09-22 10:56   ` Ted Zlatanov
2016-09-23 20:38     ` Richard Stallman
2016-09-24  2:45       ` Ted Zlatanov [this message]
2016-09-25 17:15         ` Richard Stallman
2020-08-12  1:38 ` Stefan Kangas
2022-01-29 16:51   ` Lars Ingebrigtsen

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=87intmypzs.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=24489@debbugs.gnu.org \
    --cc=larsi@gnus.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).