From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Robert Pluim Newsgroups: gmane.emacs.bugs 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 Message-ID: <874lih2oc1.fsf@gmail.com> References: <83y3fubkum.fsf@gnu.org> <83a7s9b8nv.fsf@gnu.org> <3396fe3edac96118eeaea92013f4cbd4@webmail.orcon.net.nz> <0c6052eff2cd93fe83c953b3c9d3d1da@webmail.orcon.net.nz> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1528215795 21437 195.159.176.226 (5 Jun 2018 16:23:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 5 Jun 2018 16:23:15 +0000 (UTC) Cc: 31709@debbugs.gnu.org, Lars Ingebrigtsen To: Phil Sainty Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jun 05 18:23:10 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fQEjk-0005Ra-T3 for geb-bug-gnu-emacs@m.gmane.org; Tue, 05 Jun 2018 18:23:09 +0200 Original-Received: from localhost ([::1]:47990 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fQElr-0008Kt-J4 for geb-bug-gnu-emacs@m.gmane.org; Tue, 05 Jun 2018 12:25:19 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36796) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fQElf-0008HG-8w for bug-gnu-emacs@gnu.org; Tue, 05 Jun 2018 12:25:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fQEla-0004GU-A7 for bug-gnu-emacs@gnu.org; Tue, 05 Jun 2018 12:25:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:55753) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fQEla-0004GQ-4p for bug-gnu-emacs@gnu.org; Tue, 05 Jun 2018 12:25:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fQEla-00084K-08 for bug-gnu-emacs@gnu.org; Tue, 05 Jun 2018 12:25:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Robert Pluim Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 05 Jun 2018 16:25:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 31709 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 31709-submit@debbugs.gnu.org id=B31709.152821589631001 (code B ref 31709); Tue, 05 Jun 2018 16:25:01 +0000 Original-Received: (at 31709) by debbugs.gnu.org; 5 Jun 2018 16:24:56 +0000 Original-Received: from localhost ([127.0.0.1]:35417 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fQElT-00083x-MU for submit@debbugs.gnu.org; Tue, 05 Jun 2018 12:24:55 -0400 Original-Received: from mail-wr0-f195.google.com ([209.85.128.195]:39397) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fQElS-00083k-9f for 31709@debbugs.gnu.org; Tue, 05 Jun 2018 12:24:54 -0400 Original-Received: by mail-wr0-f195.google.com with SMTP id w7-v6so3092483wrn.6 for <31709@debbugs.gnu.org>; Tue, 05 Jun 2018 09:24:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:mail-copies-to:gmane-reply-to-list :date:in-reply-to:message-id:mime-version; bh=xzeq1502EsHpJ4voJxJl0ioZUvsKjScQQTNv0nfNRCE=; b=dFKxWd08sAVf3oCaMjs2cTu2Ewsz1T2GwsZ7MQlCfiHZiggHUAJ0Djqu5JqOgs82Na gT0hHr3R1RXmAkuqEOnBrlvtLsClzb4n1fjSgbFuP4t74aG2BXeX4uFaoG0GScdDboE4 AAIWEsxAtasIqIgbeAM9NuHyxUaQFdAJG4+5F/2i9Y2aFVZI1EASS9SSYJ2X5Xd8/+sz iCetgxVJ+wsv6xjl57QI75+ub5akbEv5bBmnZ7NcJ2/o0J+O3lg4y3bg31wlXI0c3IrQ MCfhGF8afLvBRrp20Xg/9vJWrQW21qF8co4lD7DjvfAyDce+nDty4KUutOfwMIJFW92D cm7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:mail-copies-to :gmane-reply-to-list:date:in-reply-to:message-id:mime-version; bh=xzeq1502EsHpJ4voJxJl0ioZUvsKjScQQTNv0nfNRCE=; b=nv6NLcbkSp0dgPjnb29sl0OeWwjAzeR4G+/J9h/SaJjlfV+UkIyGjWx96vf4gg4Azy 5UoAKKzxEdZbypQSkvBu0VD0z/yrSDh+tu/JLMCj3lmvI3DQaHqvQ331W/riTqEto+Nj viRj5t+qozGXPKAbV5lzlQuoofiw2kA1iLl0XW+F/+HCv8ht3u2hMSU9F0ahFAsJGKvN jo7PNA7vHl06JdAPWmvw0m5I6gXHHDesBo8cj/8xCN7EDi6A2vGYxb8tIUFFrm4+b6HO eZi5Oiu4OnOKbNQQwmXpizo5X/fCqIgdk2EXEEpgkjFFpd5JZwmBaGfWSa6o8eyie1FF PHNg== X-Gm-Message-State: APt69E3vPGe4quylVU86FYU0b/koybnJ6OnW1wgGF4siAUI5k2HGPVW6 2i3CYUTQu317yztZZxE7u8c= X-Google-Smtp-Source: ADUXVKJx9lvp6r5f7w3DgR2JKJtQ0KHjx1ELS4TcdCXegCGqOQ6C5Wwrxe+SCJ+6x6oAfk0p/I5WFQ== X-Received: by 2002:adf:9b1a:: with SMTP id b26-v6mr5803920wrc.206.1528215888324; Tue, 05 Jun 2018 09:24:48 -0700 (PDT) Original-Received: from rpluim ([149.5.228.1]) by smtp.gmail.com with ESMTPSA id j13-v6sm48573278wre.38.2018.06.05.09.24.47 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 05 Jun 2018 09:24:47 -0700 (PDT) Mail-Copies-To: never Gmane-Reply-To-List: yes In-Reply-To: <0c6052eff2cd93fe83c953b3c9d3d1da@webmail.orcon.net.nz> (Phil Sainty's message of "Wed, 06 Jun 2018 03:51:10 +1200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:147037 Archived-At: Phil Sainty 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