[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode
From: |
Manuel Giraud |
Subject: |
bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode |
Date: |
Sun, 19 Mar 2023 12:43:02 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: 62260@debbugs.gnu.org
>> Date: Sat, 18 Mar 2023 22:00:32 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>>
>> > With this patch, the /tmp directory now contains an auto-save file with
>> > mode 0600.
>>
>> When a buffer visits a file, its auto-save file should have the same
>> mode bits as the file itself (modulo your umask). I see no need to
>> affect that part in any case. If the file itself is not private, why
>> should its auto-save file be private? Also, there's
>> auto-save-visited-mode.
>
> More generally: what problems are you trying to solve here? If this
> code causes some problems, please describe them, and let's see whether
> and how we should fix them.
You're right. I should have start from here. So it all start with a
recurring message I get from TRAMP whenever I access a root file (via
sudo method) for the first time. It asks:
"Autosave file on local temporary directory, do you want to continue?"
I answer "yes" but it seems that it can potentially leak root data
through auto-save files. Looking at the code that asks this question
(tramp.el:6528), I see that I can set
'tramp-allow-unsafe-temporary-files' to t and I won't see the question
again... but the leakage is still possible. So I guess what I want is
an option to stop auto-save entirely in those cases.
>From there, I've looked at how auto-save work and I ask myself: "maybe
instead of such an option, I could limit others rights on auto-save
files". And that's how I came up with this patch.
--
Manuel Giraud
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Manuel Giraud, 2023/03/18
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Eli Zaretskii, 2023/03/18
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Manuel Giraud, 2023/03/18
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Eli Zaretskii, 2023/03/18
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Eli Zaretskii, 2023/03/18
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Manuel Giraud, 2023/03/18
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Eli Zaretskii, 2023/03/18
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Eli Zaretskii, 2023/03/18
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode,
Manuel Giraud <=
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Eli Zaretskii, 2023/03/19
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Michael Albinus, 2023/03/19
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Manuel Giraud, 2023/03/19
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Michael Albinus, 2023/03/20
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Eli Zaretskii, 2023/03/20
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Michael Albinus, 2023/03/20
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Manuel Giraud, 2023/03/20
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Eli Zaretskii, 2023/03/19
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Michael Albinus, 2023/03/20
- bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode, Manuel Giraud, 2023/03/19