unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 18476@debbugs.gnu.org, Lars Ljung <lars@matholka.se>
Subject: bug#18476: 24.3.93; ede-emacs-version: Searching for program: no such file or directory, egrep
Date: Tue, 16 Sep 2014 23:33:22 +0200	[thread overview]
Message-ID: <87d2avl07x.fsf@engster.org> (raw)
In-Reply-To: <jwv4mw765qh.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Tue, 16 Sep 2014 09:50:26 -0400")

Stefan Monnier writes:
>> - has the Emacs source in a directory which is considered 'safe'
>>   (w.r.t. ede-project-directories), and
>
> I.e. either ede-project-directories explicitly accepts this particular
> directory or it's set to t.  If the dir is explicitly listed, then we
> can say "the user gets what she asked for".  But indeed if it's t we
> don't have that defense.
>
> You say "safe" but the docstring of ede-project-directories doesn't
> mention anything about safety or lack thereof.  Is it dangerous to set
> it to t?

I don't think so.

The Long Answer:

This variable was part of the EDE security fix which lead to the 23.4
release. If you remember, EDE used to simply evaluate the "Project.ede"
files to load a project - code is data, after all - but that made it
easy for an attacker to let your Emacs execute arbitrary code.

The "real" fix was that EDE now parses the Project.ede files if it
actually contains a project definition. However, that code which does
the parsing isn't really trivial, so we also added
`ede-project-directories' with 'nil' as default. The idea was that when
people create their own projects, those should get added
semi-automatically, but if you wanted to load external ones, you'd have
to add those directories by hand.

> By the way, looking at the code of ede-emacs-version, we need to fix all
> those "match-string without checking the success of the previous
> re-search-forward".

Yes, definitely. I can do that, but at least for the emacs-24 branch I
wanted to keep the patch short.

-David





  reply	other threads:[~2014-09-16 21:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-14 18:11 bug#18476: 24.3.93; ede-emacs-version: Searching for program: no such file or directory, egrep Lars Ljung
2014-09-15 20:16 ` David Engster
2014-09-16  0:17   ` Stefan Monnier
2014-09-16  6:13     ` David Engster
2014-09-16 13:50       ` Stefan Monnier
2014-09-16 21:33         ` David Engster [this message]
2014-09-17  1:05           ` Stefan Monnier
2014-09-18 20:40             ` David Engster

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=87d2avl07x.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=18476@debbugs.gnu.org \
    --cc=lars@matholka.se \
    --cc=monnier@iro.umontreal.ca \
    /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).