From: Eli Zaretskii <eliz@gnu.org>
To: Vasilij Schneidermann <mail@vasilij.de>
Cc: 62991@debbugs.gnu.org
Subject: bug#62991: 30.0.50; normal-backup-enable-predicate does not consider /dev/shm
Date: Fri, 21 Apr 2023 14:56:18 +0300 [thread overview]
Message-ID: <83cz3x4ffh.fsf@gnu.org> (raw)
In-Reply-To: <ZEJqHSyacNods6V2@odonien> (message from Vasilij Schneidermann on Fri, 21 Apr 2023 12:49:01 +0200)
> Date: Fri, 21 Apr 2023 12:49:01 +0200
> From: Vasilij Schneidermann <mail@vasilij.de>
>
> I've found that the `pass` password-store creates temporary files under
> /dev/shm rather than /tmp and editing those files with emacs creates
> backup files (which may leak passwords outside that directory if
> `backup-directory-alist` is customized to place them elsewhere)`. This
> seems to be due to `normal-backup-enable-predicate` specifically testing
> for /tmp (and two other temporary directories), but not other
> directories backed by a tmpfs file system (such as /dev/shm). There
> does not appear to be a customizable to extend the list of directories
> it's checking for either. One more candidate for exclusion is the
> /run/user/<uid> directory (it's backed by tmpfs as well, but has
> different uses).
We could indeed teach normal-backup-enable-predicate about /dev/shm on
systems where that is appropriate, but I'm curious why you say this is
not customizable: normal-backup-enable-predicate is called via a
variable, backup-enable-predicate, so you could customize that by
writing your own predicate function, and assigning
backup-enable-predicate to that function. Or what am I missing?
next prev parent reply other threads:[~2023-04-21 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 10:49 bug#62991: 30.0.50; normal-backup-enable-predicate does not consider /dev/shm Vasilij Schneidermann
2023-04-21 11:56 ` Eli Zaretskii [this message]
2023-04-21 12:10 ` Vasilij Schneidermann
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=83cz3x4ffh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62991@debbugs.gnu.org \
--cc=mail@vasilij.de \
/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).