unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Please rename trusted-content to trusted-contents
Date: Tue, 24 Dec 2024 08:32:20 +0100	[thread overview]
Message-ID: <Z2pjhMdYWklbYVAD@tuxteam.de> (raw)
In-Reply-To: <jwvy105hdby.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

On Tue, Dec 24, 2024 at 12:17:10AM -0500, Stefan Monnier wrote:
> > Isn't it the file path that is being configured and trusted rather than
> > the file content(s)?
> 
> It's arguably a philosophical question.  But what needs to be determined
> is not whether we should trust the file's name but whether we should
> trust the file's content·s.
> 
> We just happen to rely mostly on the file's name to make that decision.

Thank you for re-stating this. At some point I got tired and gave up.

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2024-12-24  7:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20  5:23 Please rename trusted-content to trusted-contents Richard Stallman
2024-12-20  7:52 ` Eli Zaretskii
2024-12-20  9:42   ` Stefan Kangas
2024-12-20 12:30     ` Eli Zaretskii
2024-12-22  4:06       ` Stefan Kangas
2024-12-22  4:36         ` Stefan Monnier
2024-12-22  4:48           ` Stefan Monnier
2024-12-22 18:01             ` Morgan Willcock
2024-12-24  5:17               ` Stefan Monnier
2024-12-24  7:32                 ` tomas [this message]
2024-12-22 18:30             ` [External] : " Drew Adams
2024-12-23  0:31               ` Björn Bidar
2024-12-24  4:53               ` Richard Stallman
2024-12-23  4:08             ` Richard Stallman
2024-12-23 13:32               ` Björn Bidar
     [not found]               ` <87ed1yv82u.fsf@>
2024-12-25  4:48                 ` Richard Stallman
2024-12-24  5:14             ` Stefan Monnier
2024-12-23  4:08     ` Richard Stallman

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=Z2pjhMdYWklbYVAD@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@gnu.org \
    /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).