unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>,
	Ulrich Mueller <ulm@gentoo.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: emacsclient startup messages
Date: Sat, 6 Nov 2021 11:40:09 -0700	[thread overview]
Message-ID: <45914742-e247-cb0c-159e-39e38ab2fb73@gmail.com> (raw)
In-Reply-To: <CAO48Bk9x-v+jiGaR2W7H4=LWh9sJvV2Uo8y_GvAX2p0c1U8hxQ@mail.gmail.com>

On 11/6/2021 4:35 AM, Pedro Andres Aranda Gutierrez wrote:
> hmmm... from a user's perspective I really don't know what I gain by 
> having emacs running as a daemon if I boot up my laptop to say watch a 
> film or listen to a recording from my satellite PVR just for the fun of it.

This is roughly in line with how I use Emacs too: I start it up, I edit 
stuff, and then when I'm done (which may take anywhere from a few 
minutes to a few weeks), I close Emacs entirely.

However, for the issue of these startup messages, I think the main thing 
we need to do here is to figure out whether the XDG_RUNTIME_DIR warning 
is a legitimate warning (i.e. it's informing the user that they're 
vulnerable to a symlink attack), and then either a) fix the 
vulnerability or b) remove the warning if there's no vuln.

I'm not an expert on this sort of security analysis, so I can't really 
say for sure whether this is a real vulnerability. However, Paul 
Eggert's message[1] agrees it *is* insecure, so it should be fixed 
(somehow). The question then would be how to close the vulnerability 
while supporting the behavior that Gentoo would like (see Ulrich's 
messages).

- Jim

[1] https://lists.gnu.org/archive/html/bug-gnu-emacs/2021-10/msg02641.html



  reply	other threads:[~2021-11-06 18:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  5:26 emacsclient startup messages Pedro Andres Aranda Gutierrez
2021-10-26 12:18 ` Eli Zaretskii
2021-10-26 16:43   ` Pedro Andres Aranda Gutierrez
2021-10-26 16:32 ` Jim Porter
2021-10-26 16:46   ` Pedro Andres Aranda Gutierrez
2021-10-26 17:03     ` Jim Porter
2021-10-27  5:05       ` Pedro Andres Aranda Gutierrez
2021-10-30 17:39   ` Ulrich Mueller
2021-10-30 19:16     ` Jim Porter
2021-10-30 19:47       ` Jim Porter
2021-10-31 10:03         ` Pedro Andres Aranda Gutierrez
2021-10-31 15:44           ` Pedro Andres Aranda Gutierrez
2021-11-05  7:04             ` Pedro Andres Aranda Gutierrez
2021-11-05  8:04               ` Eli Zaretskii
2021-11-05  9:40                 ` Ulrich Mueller
2021-11-05 16:35                   ` Jim Porter
2021-11-05 17:52                     ` Ulrich Mueller
2021-11-06 11:35                       ` Pedro Andres Aranda Gutierrez
2021-11-06 18:40                         ` Jim Porter [this message]
2021-11-07  9:49                       ` Peter Oliver

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=45914742-e247-cb0c-159e-39e38ab2fb73@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=paaguti@gmail.com \
    --cc=ulm@gentoo.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 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).