unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: acorallo@gnu.org, jm@pub.pink, monnier@iro.umontreal.ca,
	75017@debbugs.gnu.org
Subject: bug#75017: 31.0.50; Untrusted user lisp files
Date: Tue, 24 Dec 2024 14:15:16 +0200	[thread overview]
Message-ID: <86r05x2s6j.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmwdRYPVa2L4fcm4Pt+Rwa4O2Es5_VxXJNrX=szDUAGnw@mail.gmail.com> (message from Stefan Kangas on Tue, 24 Dec 2024 00:35:10 +0000)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Tue, 24 Dec 2024 00:35:10 +0000
> Cc: monnier@iro.umontreal.ca, jm@pub.pink, 75017@debbugs.gnu.org, 
> 	acorallo@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I think this is over-engineering.  Yes, there are situations where it
> > makes sense to trust site-init-file.  No, they are not 100% of the
> > possible situations.  Which in my book means we should leave it to
> > users to decide whether to trust that file or not.
> 
> How do you feel about early-init-file?

I'm with Stefan Monnier on this one: there's no urgency to make any
changes in that area.





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

Thread overview: 24+ 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 [this message]
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-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=86r05x2s6j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=75017@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=jm@pub.pink \
    --cc=monnier@iro.umontreal.ca \
    --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).