Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Package Request: Please, a sudo alternative with regex support
Date: Tue, 16 Nov 2021 12:29:18 +0100	[thread overview]
Message-ID: <20211116112918.9X8nh3T6ylJNj8fcvABXQGt-kH-IOdUUdCj11pxATaA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34101@inbox.vuxu.org>

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

Closed issue by pfr-dev on void-packages repository

https://github.com/void-linux/void-packages/issues/34101

Description:
Project URL: https://github.com/edneville/please

README.md copypasta:

> The aim is to allow admins to delegate accurate least privilege access with ease. There are times when what is intended to be executed can be expressed easily with a regex to expose only what is needed and nothing more.
>
>The idea is to help you admin your box without giving users full root shells, just because that is easier. Most admins have experience of regex in one form or another, so lets configure access that way.
>
>I saw regex but don't like regex. No problem, you can still use please without regex using `exact_` counterparts, or treat each field/property as plain text, and escape control characters `?(){}[]+` etc. Most of the regex match statements have `exact` counterparts.
>
>Please is written with memory safe rust. Traditional C memory unsafety is avoided, logic problems may still exist. Logic problems would exist in both systems, but I choose the smaller problem set.



  parent reply	other threads:[~2021-11-16 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16  2:51 [ISSUE] Package Request: Pleaser, " pfr-dev
2021-11-16 11:29 ` Package Request: Please, " paper42
2021-11-16 11:29 ` paper42 [this message]
2021-11-16 23:54 ` pfr-dev
2021-11-16 23:54 ` pfr-dev

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=20211116112918.9X8nh3T6ylJNj8fcvABXQGt-kH-IOdUUdCj11pxATaA@z \
    --to=paper42@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).