From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
Cc: emacs-devel@gnu.org
Subject: Re: SES local variables to define printers
Date: Sun, 26 May 2013 21:35:49 -0400 [thread overview]
Message-ID: <jwvhahpb440.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <801u8tcwtl.fsf@gmail.com> ("Vincent Belaïche"'s message of "Sun, 26 May 2013 22:25:58 +0200")
> That would not really make it safer because any hacker could find the
> `somewhere in the file' and put some malicious definition there.
You'd check the function's safety when reading the file, of course, as
it is done currently for the `printer' arg of ses-cell.
> My concern was more about getting the system stuck, but you still have
> the C-g
Exactly: it allows denial-of-service kinds of attacks, but you can
probably already get similar problems some other way (e.g. provide
a `printer' argument that's a circular structure, so that the safety
checking doesn't terminate).
Stefan
next prev parent reply other threads:[~2013-05-27 1:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 20:25 SES local variables to define printers Vincent Belaïche
2013-05-27 1:35 ` Stefan Monnier [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-30 15:36 Vincent Belaïche
2013-05-30 17:15 ` Stefan Monnier
2013-05-30 7:24 Vincent Belaïche
2013-05-30 5:50 Vincent Belaïche
2013-05-30 13:20 ` Stefan Monnier
2013-05-28 4:38 Vincent Belaïche
2013-05-28 4:57 ` Stefan Monnier
2013-05-26 7:16 Vincent Belaïche
2013-05-26 18:02 ` Stefan Monnier
2013-05-25 20:43 Vincent Belaïche
2013-05-26 1:17 ` Stefan Monnier
2013-05-24 5:53 Vincent Belaïche
2013-05-24 5:46 Vincent Belaïche
2013-05-24 5:45 Vincent Belaïche
2013-05-24 13:28 ` Stefan Monnier
2013-05-23 20:52 Vincent Belaïche
2013-05-23 21:35 ` Davis Herring
2013-05-24 1:06 ` Glenn Morris
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=jwvhahpb440.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=vincent.b.1@hotmail.fr \
/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.