From: Hoshpak <Hoshpak@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update INSTALL.msg
Date: Fri, 10 Apr 2020 09:11:27 +0200 [thread overview]
Message-ID: <20200410071127.AJLyJbE1JiOKESpB31k84sab9PeOJMdbZjvfOhqfiPY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20816@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/pull/20816#issuecomment-611911252
Comment:
I'm going to reject this. This would require a user to set up sudo first and grant the user executing the commands to either specififcally the permission to execute these commands as root or all commands. Furthermore it should be clear to most if not all people that these commands require root rights (the xbps command displaying it requires you to run it with root rights) and sudo is not the only way to escalate privileges.
next prev parent reply other threads:[~2020-04-10 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 2:13 [PR PATCH] " ethieda
2020-04-10 7:11 ` Hoshpak [this message]
2020-04-10 7:11 ` [PR PATCH] [Closed]: " Hoshpak
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=20200410071127.AJLyJbE1JiOKESpB31k84sab9PeOJMdbZjvfOhqfiPY@z \
--to=hoshpak@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).