unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Closing a privilege escalation
Date: Thu, 26 Apr 2018 17:05:23 -0400	[thread overview]
Message-ID: <E1fBo4x-00027X-Ey@fencepost.gnu.org> (raw)
In-Reply-To: <m3muxqcu23.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu,  26 Apr 2018 09:20:52 +0200)

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

  > I thought the discussion concluded that a sudo user can do anything
  > (like put stuff in root's ~/.bashrc), and that this isn't something that
  > Emacs should worry about.

A sudo-capable user can do all sorts of bad things while sudoing,
but that's not what we are talkin about.
Here the issue is what malicious code can do, while that user is NOT sudoing,
to arrange to take advantage later.  One way is by editing .emacs
so that it will do something bad next time the user runs Emacs under sudo.

Unfortunately, it seems there are many ways the code could do that,
which do not work by editing .emacs.  So trying to block that avenue
is ineffective.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.




  parent reply	other threads:[~2018-04-26 21:05 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 [this message]
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
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

  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=E1fBo4x-00027X-Ey@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).