unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: znavko@disroot.org
Cc: help-guix@gnu.org
Subject: Re: How to allow usual users use protonvpn binary and connect
Date: Wed, 24 Feb 2021 21:54:45 +0100	[thread overview]
Message-ID: <87im6h9ofe.fsf@web.de> (raw)
In-Reply-To: <5127035c9554b931b3f463fcb6900252@disroot.org>

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


znavko--- via <help-guix@gnu.org> writes:

> I need to connect or disconnect protonvpn manually when I want.
> And type root password for that is too much.
> If usual user can run

with usual user you mean people allowed to invoke sudo?

> $ sudo protonvpn c
> with no ay password required, it will be fine!
>
> But I don't know how to type it in my config.
> just adding protonvpn in my existing perfectly working rule givesthe error:
>
> (define %sudoers-specification
>  (plain-file "sudoers" "root ALL=(ALL) ALL
> %wheel ALL=(ALL) ALL
> %wheel ALL=(root) NOPASSWD: /usr/scripts/*, /wpa, protonvpn"))

They must be in the wheel-group for this to work.

> Also if I define full path to protonvpn binary in /gnu/store that does not work too.

This is something I use:

%wheel ALL=(ALL) NOPASSWD: /run/current-system/profile/bin/cpupower

It requires cpupower to be installed as package via /etc/config.scm

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

      reply	other threads:[~2021-02-24 20:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 20:09 How to allow usual users use protonvpn binary and connect znavko--- via
2021-02-24 20:54 ` Dr. Arne Babenhauserheide [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87im6h9ofe.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=help-guix@gnu.org \
    --cc=znavko@disroot.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 read-only IMAP folder(s) and NNTP newsgroup(s).