From: Robin Tarsiger <rtt@dasyatidae.com>
To: emacs-devel@gnu.org
Subject: Re: Access control in Emacs?
Date: Wed, 15 Sep 2021 15:21:34 -0500 [thread overview]
Message-ID: <aa8d0c67-1f4f-22a4-62db-3b3034204820@dasyatidae.com> (raw)
In-Reply-To: <jwvr1drfdbo.fsf-monnier+emacs@gnu.org>
Stefan Monnier wrote:
>> I’m adding more powerful features to crdt.el including buffer local variable
>> synchronizations and arbitrary remote command/function call,
>
> Given the way Emacs is designed/structured this is a recipe for big
> gaping security holes. It can be OK to allow such things for *very*
> specific cases (a few specific well understood variables), but even such
> a "whitelist" is a problem because it requires careful and
> long term maintenance.
For the buffer-local variables specifically, we do already have
safe-local-variable-p which might cover a number of cases---and
that's already used for loading variables from untrusted files.
That said, that mechanism is still dangerous on an absolute scale
and has had security holes in the past (one of which I PoC'd and
reported myself decades ago, though I can't find it now).
Remote commands would be even more dangerously tricky to get right,
especially in the absence of ground-up infrastructure for it.
-RTT
next prev parent reply other threads:[~2021-09-15 20:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 12:49 Access control in Emacs? Qiantan Hong
2021-09-14 14:09 ` Phil Sainty
2021-09-14 14:28 ` dick
2021-09-14 15:05 ` Qiantan Hong
2021-09-14 15:52 ` dick
2021-09-14 16:02 ` Stefan Kangas
2021-09-14 14:49 ` Stefan Monnier
2021-09-15 20:11 ` Richard Stallman
2021-09-15 20:21 ` Robin Tarsiger [this message]
2021-09-14 18:13 ` Christine Lemmer-Webber
2021-09-14 19:59 ` tomas
2021-09-15 23:16 ` Qiantan Hong
2021-09-16 2:16 ` Christine Lemmer-Webber
2021-09-18 0:29 ` 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=aa8d0c67-1f4f-22a4-62db-3b3034204820@dasyatidae.com \
--to=rtt@dasyatidae.com \
--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.