From: Eli Zaretskii <eliz@gnu.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 70440@debbugs.gnu.org, kobarity@gmail.com
Subject: bug#70440: [PATCH] Use -P switch when calling 'python-interpreter'
Date: Fri, 19 Apr 2024 20:31:01 +0300 [thread overview]
Message-ID: <86y1999s4q.fsf@gnu.org> (raw)
In-Reply-To: <87bk65gxdk.fsf@gmail.com> (message from Augusto Stoffel on Fri, 19 Apr 2024 17:55:51 +0200)
> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: kobarity@gmail.com, 70440@debbugs.gnu.org
> Date: Fri, 19 Apr 2024 17:55:51 +0200
>
> On Fri, 19 Apr 2024 at 18:40, Eli Zaretskii wrote:
>
> > I'm not sure I understand: if the user doesn't have a version of
> > Python which supports this option, what else can we do? Refuse to
> > use such a Python? That doesn't seem to be an option we can use.
>
> Why not?
Because it's unthinkable?
> Let me make sure we're on the same page that this affects only
> couple of handy but by no means essential commands that add or remove
> import statements. Nobody _needs_ this to write Python code.
That's not relevant. The important part is that if we accept your
proposal, users who have Python that doesn't support -P will be unable
to invoke Python even if their Python programs don't use the
problematic features.
> > Yes, this is a security hole, but it's the user's security hole, not
> > ours, if the user doesn't install the safer Python.
>
> I see it as _my_ security hole, since it was me who added a line to
> Emacs that calls 'python -c' in a random directory without removing the
> current directory from the module load path (as much as a find it a bad
> design choice in Python to do that by default.)
Sorry, you lost me here. But if there's a way to close the hole
without preventing users to use a subordinate Python, please describe
it in more details.
next prev parent reply other threads:[~2024-04-19 17:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 18:23 bug#70440: [PATCH] Use -P switch when calling 'python-interpreter' Augusto Stoffel
2024-04-17 19:13 ` Eli Zaretskii
2024-04-18 15:25 ` kobarity
2024-04-18 15:52 ` Augusto Stoffel
2024-04-18 15:57 ` Eli Zaretskii
2024-04-18 16:02 ` Augusto Stoffel
2024-04-18 16:13 ` Eli Zaretskii
2024-04-19 6:08 ` Augusto Stoffel
2024-04-19 7:15 ` Eli Zaretskii
2024-04-19 15:21 ` Augusto Stoffel
2024-04-19 15:40 ` Eli Zaretskii
2024-04-19 15:55 ` Augusto Stoffel
2024-04-19 17:31 ` Eli Zaretskii [this message]
2024-04-19 18:02 ` Augusto Stoffel
2024-04-19 18:17 ` Eli Zaretskii
2024-04-19 18:30 ` Augusto Stoffel
2024-04-19 19:01 ` Eli Zaretskii
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=86y1999s4q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70440@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=kobarity@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).