From: Davis Herring <herring@lanl.gov>
To: Richard Stallman <rms@gnu.org>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Closing a privilege escalation
Date: Wed, 25 Apr 2018 09:25:15 -0600 [thread overview]
Message-ID: <2f1d5ab7-f517-caab-749b-27217c45a995@lanl.gov> (raw)
In-Reply-To: <E1fB8vq-0002wh-19@fencepost.gnu.org>
> With some arguments, emacs started inside sudo will run the user's own
> .emacs file rather than root's. This creates a known vulnerability
> for privilege escalation.
How does .emacs allow additional access? Anyone who can run emacs as
root can run anything as root (via M-!, among many many other
possibilities that cannot be countered by noexec).
> For sudo-authorized users, require .emacs (and other Emacs startup
> files and directories) to be owned by root.
>
> This won't be a big hassle for them, since
> these users can sudo to edit their root-owned files.
> > Do people see any problem with this?
It could easily be a problem if, say, .emacs is under version control.
It might also interfere with backup systems, and could be incompatible
with home directories mounted in special ways (e.g., NFS).
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2018-04-25 15:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 1:09 Closing a privilege escalation Richard Stallman
2018-04-25 1:18 ` Noam Postavsky
2018-04-25 22:40 ` Richard Stallman
2018-04-25 1:29 ` Lars Ingebrigtsen
2018-04-25 22:40 ` Richard Stallman
2018-04-26 7:20 ` Lars Ingebrigtsen
2018-04-26 7:52 ` Lars Ingebrigtsen
2018-04-26 21:05 ` Richard Stallman
2018-04-26 21:26 ` Tim Cross
2018-04-27 15:57 ` Richard Stallman
2018-04-27 9:50 ` Marcin Borkowski
2018-04-27 14:29 ` Clément Pit-Claudel
2018-04-25 15:25 ` Davis Herring [this message]
2018-04-25 16:47 ` Glenn Morris
2018-04-25 17:09 ` Stefan Monnier
2018-04-25 17:12 ` Stefan Monnier
2018-04-25 17:55 ` Paul Eggert
2018-04-26 21:01 ` Richard Stallman
2018-04-25 17:10 ` Søren Pilgård
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=2f1d5ab7-f517-caab-749b-27217c45a995@lanl.gov \
--to=herring@lanl.gov \
--cc=emacs-devel@gnu.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 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.