From: Robert Pluim <rpluim@gmail.com>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 31709@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#31709: 27.0.50; Wishlist: Perhaps Emacs should load a file when getting a particular signal?
Date: Tue, 05 Jun 2018 18:24:46 +0200 [thread overview]
Message-ID: <874lih2oc1.fsf@gmail.com> (raw)
In-Reply-To: <0c6052eff2cd93fe83c953b3c9d3d1da@webmail.orcon.net.nz> (Phil Sainty's message of "Wed, 06 Jun 2018 03:51:10 +1200")
Phil Sainty <psainty@orcon.net.nz> writes:
> On 2018-06-06 03:35, Phil Sainty wrote:
>> On 2018-06-06 02:38, Eli Zaretskii wrote:
>>> Having a fixed file name in Emacs that is loaded by an external signal
>>> would be a terrible security risk, no?
>>
>> Bad Things could surely be done; but if the attacker has access to
>> send signals to the user's emacs process or write files in the user's
>> ~/.emacs.d directory, has a terrible security breach not already
>> occurred? The notion of an attacker gaining access to a running Emacs
>> session is certainly bad, but I'm unsure whether the proposed idea
>> really worsens the risk in principle?
>
> In fact if you normally run emacs as a server you're opening up the
> same security risk, no? An attacker who could send a signal to an
> emacs process can also run emacsclient to access an existing server;
> and I don't think we consider the practice of running an emacs server
> to be a terrible security risk.
What if this hypothetical emacs was deliberately started without a
server running, since it contains sensitive information? Starting a
server when receiving a signal has now opened up access to that emacs
where none existed before.
Robert
next prev parent reply other threads:[~2018-06-05 16:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 11:29 bug#31709: 27.0.50; Wishlist: Perhaps Emacs should load a file when getting a particular signal? Lars Ingebrigtsen
2018-06-04 12:27 ` Marcin Borkowski
2018-06-05 13:27 ` Lars Ingebrigtsen
2018-06-04 14:52 ` João Távora
2018-06-05 13:28 ` Lars Ingebrigtsen
2018-06-04 16:02 ` Eli Zaretskii
2018-06-05 13:31 ` Lars Ingebrigtsen
2018-06-05 14:28 ` Phil Sainty
2018-06-05 14:38 ` Eli Zaretskii
2018-06-05 15:21 ` Lars Ingebrigtsen
2018-06-05 15:45 ` Eli Zaretskii
2018-06-05 16:20 ` Robert Pluim
2018-06-05 15:35 ` Phil Sainty
2018-06-05 15:51 ` Phil Sainty
2018-06-05 16:24 ` Robert Pluim [this message]
2018-06-05 16:36 ` Phil Sainty
2018-06-05 17:05 ` Phil Sainty
2019-09-21 8:19 ` Lars Ingebrigtsen
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=874lih2oc1.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=31709@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=psainty@orcon.net.nz \
/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).