From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] spiped: add unprivileged system account
Date: Tue, 08 Jun 2021 10:38:30 +0200 [thread overview]
Message-ID: <20210608083830.UCkcd9GmJ-mqGkpXdTph5ZW-pIhP11VTrHGXkzLZMeg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31332@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
New review comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/31332#discussion_r647237436
Comment:
There are no configure options as by default spiped runs with the current user privileges, unless the -u option is passed.
It's so that an account doesn't have to be created manually and so that we have "standardized" sandbox accounts as much as possible.
Ideally this would be accompanied by a sv script, but given that a tunnel can be created for any arbitrary service/port I wasn't sure if I should provide one. Would it make sense to provide a run script that needs a related conf file (for configuring the various options)? Also, that would cover a single tunnel instance only, anyone that needs more would need to create more services (e.g. /etc/sv/spiped-tunnel-N etc.).
next prev parent reply other threads:[~2021-06-08 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 23:22 [PR PATCH] " ailiop-git
2021-06-08 2:16 ` [PR REVIEW] " ericonr
2021-06-08 8:38 ` ailiop-git [this message]
2021-06-09 0:56 ` sgn
2021-06-09 10:03 ` ailiop-git
2022-05-21 2:00 ` github-actions
2022-06-04 2:09 ` [PR PATCH] [Closed]: " github-actions
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=20210608083830.UCkcd9GmJ-mqGkpXdTph5ZW-pIhP11VTrHGXkzLZMeg@z \
--to=ailiop-git@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).