From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 43851-done@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#43851: [PATCH] gnu: sudo: Depend on python-minimal instead of python.
Date: Fri, 09 Oct 2020 21:48:22 +0200 [thread overview]
Message-ID: <87d01rrxix.fsf@gnu.org> (raw)
In-Reply-To: <87imbjz148.fsf@nckx> (Tobias Geerinckx-Rice's message of "Fri, 09 Oct 2020 20:48:55 +0200")
Tobias Geerinckx-Rice writes:
Hello!
> Maxim Cournoyer 写道:
>> If we don't have any use for it, I think it may be better to let the
>> dependency go altogether, to keep sudo as small and secure as
>> possible.
>
> I don't think sudo is either, nor does the presence of Python affect
> that meaningfully. But let's stop this pointless discussion since
> removing it helps the Hurd progress. That's enough.
>
> The Hurd is a lot more exciting than the removal of sudo Python
> support -- and actually *will* improve security!
Thanks all, I've removed the python dependency from sudo; pushed to
master as 165e0918da54643bfaf9a6cb6b866f8692e9f8f9.
Greetings,
Janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2020-10-09 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 17:04 [bug#43851] [PATCH] gnu: sudo: Depend on python-minimal instead of python Jan Nieuwenhuizen
2020-10-07 21:18 ` Tobias Geerinckx-Rice via Guix-patches via
2020-10-09 17:18 ` Jan Nieuwenhuizen
2020-10-09 18:15 ` Maxim Cournoyer
2020-10-09 18:48 ` Tobias Geerinckx-Rice via Guix-patches via
2020-10-09 19:26 ` zimoun
2020-10-09 19:44 ` Tobias Geerinckx-Rice via Guix-patches via
2020-10-09 19:53 ` Jan Nieuwenhuizen
2020-10-09 19:48 ` Jan Nieuwenhuizen [this message]
2020-10-08 7:03 ` Danny Milosavljevic
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d01rrxix.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=43851-done@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=me@tobias.gr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.