all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: rms@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Closing a privilege escalation
Date: Fri, 27 Apr 2018 07:26:19 +1000	[thread overview]
Message-ID: <CAC=50j-NXvNRP-pZigtTj5gX=j+GLTdWue+KZTCk0P8sm8AkEQ@mail.gmail.com> (raw)
In-Reply-To: <E1fBo4x-00027X-Ey@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]

Agree. I don't think this is an issue emacs can address. It is really about
how sudo is configured. On many systems, users with the 'admin' privilege
can run sudo to execute any command, including sudo su - root. Once you
have root, game over - e.g. I can easily edit .emacs of any user and there
is little emacs can do to detect that (unless you want to go the over kill
route of requiring a gpg key at startup to allow emacs to read an encrypted
.emacs or similar). As Lars points out, once you have root, you can just as
easily compromise some other part of the system or install a key logger or
even a modified version of emacs itself.

On 27 April 2018 at 07:05, Richard Stallman <rms@gnu.org> wrote:

> [[[ 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.
>
>
>


-- 
regards,

Tim

--
Tim Cross

[-- Attachment #2: Type: text/html, Size: 2865 bytes --]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC=50j-NXvNRP-pZigtTj5gX=j+GLTdWue+KZTCk0P8sm8AkEQ@mail.gmail.com' \
    --to=theophilusx@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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.