From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Daniel Mendler <mail@daniel-mendler.de>, 74879@debbugs.gnu.org
Subject: bug#74879: 30.0.92; trusted-content-p and trusted-files cannot be used for non-file buffers
Date: Sun, 15 Dec 2024 15:55:10 +0100 [thread overview]
Message-ID: <m2y10hf12p.fsf@gmail.com> (raw)
In-Reply-To: <jwvikrlukf7.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 15 Dec 2024 09:03:18 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Thank you for the recent addition of `trusted-content-p'. Is there a
>> possibility to use `trusted-content-p' in buffers which are not backed
>> by a file? I use Flymake in *scratch* or similar buffers and it seems
>> that this won't continue to work given that `trusted-content-p' needs a
>> `buffer-file-truename'.
>
> Good question.
> We don't really have a good answer yet, AFAIK, in large part because we
> don't have enough experience with it.
> Off the top of my head, here are some elements relevant to this
> discussion, in random order:
>
> - The current setup is a kind of "minimal" change for Emacs-30 because
> it's late in the pretest, so as much as possible we should separate
> the discussion into what's a simple enough solution for Emacs-30 and
> what we should use in the longer term.
>
> - You should be able to get fully-featured Flymake in *scratch*
> with (setq-local trusted-files :all).
> Maybe we should do that when we setup *scratch*?
> Which other non-file buffers would need that? The minibuffer?
>
> - Trust sucks, so we really should work on better solutions where we
> don't need to rely on trust, such as running code in `bwrap` or other
> kinds of sandboxes.
>
> - I think we do want some kind of hook, with which we can have (for
> instance) `emacs-lisp-mode` tell Emacs to trust the user init file,
> the early-init file, the custom-file, and all the files in
> `load-path`.
>
> - There is overlap with `safe-local-variable-directories`,
> `enable-local-variables` and it would be nice to consolidate (which
> can require delicate timing if we want the major mode to inform which
> content to trust).
>
Random thought:
- What if a user pastes text from a untrusted source to a trusted buffer?
- Is taint checking relevant in this context?
https://en.wikipedia.org/wiki/Taint_checking
next prev parent reply other threads:[~2024-12-15 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 0:39 bug#74879: 30.0.92; trusted-content-p and trusted-files cannot be used for non-file buffers Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-15 10:16 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-15 10:47 ` Eli Zaretskii
2024-12-15 10:56 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-15 11:18 ` Eli Zaretskii
2024-12-15 11:37 ` Ihor Radchenko
2024-12-15 12:29 ` Eli Zaretskii
2024-12-15 12:50 ` Ihor Radchenko
2024-12-15 13:38 ` Eli Zaretskii
2024-12-15 13:46 ` Stefan Kangas
2024-12-15 14:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-15 14:30 ` Stefan Kangas
2024-12-15 14:55 ` Gerd Möllmann [this message]
2024-12-15 15:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-15 15:16 ` Gerd Möllmann
2024-12-15 18:38 ` Daniel Mendler 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=m2y10hf12p.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=74879@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
/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).