From: Phil Sainty <psainty@orcon.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31709@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
bug-gnu-emacs
<bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org>
Subject: bug#31709: 27.0.50; Wishlist: Perhaps Emacs should load a file when getting a particular signal?
Date: Wed, 06 Jun 2018 03:35:01 +1200 [thread overview]
Message-ID: <3396fe3edac96118eeaea92013f4cbd4@webmail.orcon.net.nz> (raw)
In-Reply-To: <83a7s9b8nv.fsf@gnu.org>
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?
-Phil
next prev parent reply other threads:[~2018-06-05 15:35 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 [this message]
2018-06-05 15:51 ` Phil Sainty
2018-06-05 16:24 ` Robert Pluim
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3396fe3edac96118eeaea92013f4cbd4@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=31709@debbugs.gnu.org \
--cc=bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org \
--cc=eliz@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 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.