From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Closing a privilege escalation
Date: Thu, 26 Apr 2018 09:52:34 +0200 [thread overview]
Message-ID: <m3bme6csl9.fsf@gnus.org> (raw)
In-Reply-To: <m3muxqcu23.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 26 Apr 2018 09:20:52 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Richard Stallman <rms@gnu.org> writes:
>
>> The discussion reached the conclusion that the problem is real, even
>> with recent GNU/Linux systems. We have not fixed it.
>
> 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.
Oh, I see: The sploit here is that somebody has access to a user's
account, but doesn't know what the user's password is? So they place
something in the user's .emacs file that'll be run after the user does a
sudo and then starts Emacs as root?
Sounds kinda cumbersome when the attacker could just install a keylogger
for the user and so on...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2018-04-26 7:52 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 [this message]
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
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=m3bme6csl9.fsf@gnus.org \
--to=larsi@gnus.org \
--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.