From: Yuri Khan <yurivkhan@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: emacsclient socket ownership
Date: Fri, 2 Nov 2018 23:53:03 +0700 [thread overview]
Message-ID: <CAP_d_8Vjm6-gjhvki9+-SSzUPgdbvfj9xjU3gdo0tLmEAeBn=Q@mail.gmail.com> (raw)
In-Reply-To: <jwvefc3a4cf.fsf-monnier+gmane.emacs.devel@gnu.org>
On Fri, Nov 2, 2018 at 10:39 PM Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
> > It checks if the socket is owned by the same user (function socket_status).
> > If the user is root, however, this check is ignored (master emacsclient
> > line 1370). Is this not a security issue? Any user can create a socket
> > /tmp/emacs0/server, and root emacsclient will use it.
>
> Sounds like a security issue, yes: root may end up talking to some other
> user's Emacs.
Talking, in and of itself, is not a vulnerability. Can the limited
user’s server.el actually entice the root’s emacsclient to do
something that user would not be able to do?
next prev parent reply other threads:[~2018-11-02 16:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 16:43 emacsclient socket ownership Glenn Morris
2018-11-02 15:38 ` Stefan Monnier
2018-11-02 16:53 ` Yuri Khan [this message]
2018-11-02 18:49 ` Stefan Monnier
2018-11-02 20:08 ` Paul Eggert
2018-11-02 20:30 ` Stefan Monnier
2018-11-02 21:06 ` Paul Eggert
2018-11-05 1:13 ` Glenn Morris
2018-11-05 4:46 ` Stefan Monnier
2018-11-05 7:26 ` Paul Eggert
2018-11-06 17:19 ` Daniel Pittman
2018-11-06 17:54 ` Stefan Monnier
2018-11-06 18:17 ` Paul Eggert
2018-11-13 18:21 ` Glenn Morris
2018-11-13 19:25 ` Eli Zaretskii
2018-11-05 5:12 ` Paul Eggert
2018-12-05 18:53 ` Michael Heerdegen
2018-12-05 19:38 ` Glenn Morris
2018-12-05 19:46 ` Eli Zaretskii
2018-12-05 20:02 ` Glenn Morris
2018-12-05 20:19 ` Eli Zaretskii
2018-12-06 0:36 ` Paul Eggert
2018-12-06 6:37 ` Eli Zaretskii
2018-12-06 19:08 ` Paul Eggert
2018-12-06 19:18 ` Eli Zaretskii
2018-12-06 20:26 ` Glenn Morris
2018-12-06 21:01 ` Paul Eggert
2018-12-05 20:33 ` Glenn Morris
2018-12-05 20:58 ` Michael Heerdegen
2018-12-06 0:49 ` Paul Eggert
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='CAP_d_8Vjm6-gjhvki9+-SSzUPgdbvfj9xjU3gdo0tLmEAeBn=Q@mail.gmail.com' \
--to=yurivkhan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).