From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67323@debbugs.gnu.org
Subject: bug#67323: 30.0.50; [PATCH] Set a new desktop file to mode 0600
Date: Tue, 21 Nov 2023 14:00:28 +0100 [thread overview]
Message-ID: <87edgj6z2r.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <835y1vi92r.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 21 Nov 2023 14:29:00 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Tue, 21 Nov 2023 11:23:56 +0100
>> From: Manuel Giraud via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> As a desktop file can contain some "secret" data, I think it is better
>> to make it read/write only to the user by default. This does not
>> prevent the user to later change the mode of this desktop file if he
>> wants to "share" it.
>
> We don't do this in other cases, AFAICT, so why do it here?
Hi Eli,
I had this idea while browsing savehist.el. It have
'savehist-file-modes' set to #o600 by default. Since desktop.el could
also contain histories or others "secrets", I thought that it may a good
idea to have more strict default.
> The users can make this file unreadable by others if they want.
Yes and it is what I have done previously for my own desktop file. The
idea here is to have saner default. And as I said, it also works the
other way around ;-)
> It's a backward-incompatible change in any case.
You are saying that it might surprise users who rely on the "readable
for all" nature of one desktop file by default? I'd have a hard time to
figure out such a scenario… But anyway, if you think this patch does
not worth it, say it and I'll close this report.
Thanks,
--
Manuel Giraud
next prev parent reply other threads:[~2023-11-21 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 10:23 bug#67323: 30.0.50; [PATCH] Set a new desktop file to mode 0600 Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-21 12:29 ` Eli Zaretskii
2023-11-21 13:00 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-11-21 13:06 ` Eli Zaretskii
2023-12-15 1:17 ` Stefan Kangas
2023-12-15 8:37 ` Eli Zaretskii
2023-12-15 9:00 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87edgj6z2r.fsf@ledu-giraud.fr \
--to=bug-gnu-emacs@gnu.org \
--cc=67323@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=manuel@ledu-giraud.fr \
/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).