Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] explicitly allow setuid and setgid permissions in templates
Date: Tue, 27 Jul 2021 19:42:34 +0200	[thread overview]
Message-ID: <20210727174234.vBxfbB4X2sN7Hka5YvcxGPCFN8q3s4nkEteMjC2yTyw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32156@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/32156#issuecomment-887705175

Comment:
```
-rwsr-xr-x 0/0           22592 2021-05-25 07:25 ./usr/lib/electron10/chrome-sandbox
-rwsr-xr-x 0/0           22592 2021-07-11 15:30 ./usr/lib/electron12/chrome-sandbox
-rwsr-xr-x 0/0           22512 2020-09-06 11:43 ./usr/lib/electron7/chrome-sandbox
-rwsr-xr-x 0/0           22408 2021-01-22 10:00 ./usr/lib/electron9/chrome-sandbox
```

can probably be removed from the package, we should be using the user namespace sandbox by now.

I wonder if the mount utilities need suid? Shouldn't `mount` itself being suid be enough?

Curious what `cgi-wrapper` from `hiawatha` needs suid for...

As discussed over IRC, `vpsm` being suid doesn't make a difference, since it's a shell script, but it needs to be fixed.

  parent reply	other threads:[~2021-07-27 17:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 14:03 [ISSUE] " paper42
2021-07-23 14:35 ` ericonr
2021-07-26 12:10 ` fosslinux
2021-07-26 13:33 ` paper42
2021-07-26 13:33 ` paper42
2021-07-26 13:33 ` paper42
2021-07-27 16:13 ` Duncaen
2021-07-27 16:13 ` Duncaen
2021-07-27 17:42 ` ericonr [this message]
2022-05-30  2:15 ` github-actions
2022-08-17  1:48 ` CameronNemo
2022-08-17  2:43 ` ericonr

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=20210727174234.vBxfbB4X2sN7Hka5YvcxGPCFN8q3s4nkEteMjC2yTyw@z \
    --to=ericonr@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).