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: 62260@debbugs.gnu.org
Subject: bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode
Date: Sat, 18 Mar 2023 20:16:08 +0100 [thread overview]
Message-ID: <87mt49na4n.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <83bkkpc2x6.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 18 Mar 2023 20:47:17 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> I've tried it but I'm not able to come with such an example. With this
>> patch, the auto-save file has always a mode of 0600 even for a file with
>> a mode of 0006 not own by me.
>
> Did you try a different user?
I've just tried but with sudo over TRAMP. I had a message about the
lock that I stole and then Emacs created another auto-save file with
TRAMP naming (this file is also mode 0600).
I guess that using TRAMP is cheating here and that I should really be
another user using Emacs and trying to open this same file... Then I
guess I won't be able to recover from (or write to) this auto-save file.
But does this kind of scenarios appear in real life?
--
Manuel Giraud
prev parent reply other threads:[~2023-03-18 19:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 15:18 bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 15:43 ` Eli Zaretskii
2023-03-18 18:39 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 18:47 ` Eli Zaretskii
2023-03-18 18:51 ` Eli Zaretskii
2023-03-18 19:22 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 20:00 ` Eli Zaretskii
2023-03-18 20:21 ` Eli Zaretskii
2023-03-19 11:43 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-19 12:19 ` Eli Zaretskii
2023-03-19 12:40 ` Michael Albinus
2023-03-19 13:56 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-20 11:41 ` Michael Albinus
2023-03-20 12:22 ` Eli Zaretskii
2023-03-20 12:31 ` Michael Albinus
2023-03-20 14:15 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-19 14:11 ` Eli Zaretskii
2023-03-20 11:43 ` Michael Albinus
2023-03-19 14:18 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-20 11:44 ` Michael Albinus
2023-03-22 10:13 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-23 16:26 ` Michael Albinus
2023-03-24 7:34 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-24 10:35 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-24 17:56 ` Michael Albinus
2023-03-18 19:16 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87mt49na4n.fsf@ledu-giraud.fr \
--to=bug-gnu-emacs@gnu.org \
--cc=62260@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).