unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 75017@debbugs.gnu.org
Cc: jm@pub.pink, dmitry@gutov.dev, stefankangas@gmail.com,
	eliz@gnu.org, spwhitton@spwhitton.name, monnier@iro.umontreal.ca
Subject: bug#75017: 31.0.50; Untrusted user lisp files
Date: Sun, 29 Dec 2024 21:14:25 +0200	[thread overview]
Message-ID: <27858.2300919638$1735499729@news.gmane.org> (raw)
In-Reply-To: <jwvttanamdv.fsf-monnier+emacs@gnu.org> (Stefan Monnier via's message of "Sat, 28 Dec 2024 09:57:24 -0500")

Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:

>> For Debian we'll probably patch in so everything that we install on
>> the system is automatically trusted.
>
> Sounds fine, yes.

IMHO this probably applies to all distributions.

Is site-lisp not trusted by default when launching with
site-lisp/site-init enabled?





  parent reply	other threads:[~2024-12-29 19:14 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-21 20:48 bug#75017: 31.0.50; Untrusted user lisp files john muhl
2024-12-22  2:47 ` Stefan Kangas
2024-12-22  3:16   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-22  6:12     ` Eli Zaretskii
2024-12-22 17:36       ` Stefan Kangas
2024-12-22 18:41         ` Eli Zaretskii
2024-12-22 18:47           ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-23 14:10           ` Stefan Kangas
2024-12-23 14:29             ` Eli Zaretskii
2024-12-24  0:35               ` Stefan Kangas
2024-12-24 12:15                 ` Eli Zaretskii
2024-12-23 19:15             ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-22  6:19 ` Eli Zaretskii
2024-12-22 17:20   ` Stefan Kangas
2024-12-22 18:38     ` Eli Zaretskii
2024-12-22 19:52       ` Dmitry Gutov
2024-12-22 20:23         ` Eli Zaretskii
2024-12-22 20:27           ` Dmitry Gutov
     [not found]             ` <865xna60oj.fsf@gnu.org>
2024-12-23 14:36               ` Stefan Kangas
2024-12-24 23:29               ` Dmitry Gutov
2024-12-27  7:39                 ` Sean Whitton
2024-12-27  8:35                   ` Eli Zaretskii
2024-12-27 13:36                     ` Sean Whitton
2024-12-28 12:30                       ` Eli Zaretskii
2024-12-28 14:57                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 19:13                     ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 19:13                     ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 19:13                     ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 19:13                     ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 19:14                     ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-29 19:14                     ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 19:14                     ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 19:14                     ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-31  4:43                   ` Richard Stallman
2024-12-23  0:32   ` john muhl
     [not found]     ` <86v7va4kj6.fsf@gnu.org>
2024-12-23 17:53       ` john muhl
2024-12-24  5:48       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-24 23:58         ` Stefan Kangas

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='27858.2300919638$1735499729@news.gmane.org' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=75017@debbugs.gnu.org \
    --cc=bjorn.bidar@thaodan.de \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=jm@pub.pink \
    --cc=monnier@iro.umontreal.ca \
    --cc=spwhitton@spwhitton.name \
    --cc=stefankangas@gmail.com \
    /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).