unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: raingloom <raingloom@riseup.net>
To: Paul Jewell <paul@teulu.org>
Cc: Guix Bugs <bug-guix@gnu.org>, help-guix@gnu.org
Subject: nmtui - user authorisation
Date: Thu, 30 Dec 2021 20:00:23 +0100	[thread overview]
Message-ID: <20211230200023.7aec38ae@riseup.net> (raw)
In-Reply-To: <e5042cd0-ddfc-af86-abec-daeee2207e18@teulu.org>

On Wed, 29 Dec 2021 11:04:39 +0000
Paul Jewell <paul@teulu.org> wrote:

> On 29/12/2021 00:50, raingloom wrote:
> > On Tue, 28 Dec 2021 18:39:52 +0000
> > Paul Jewell<paul@teulu.org>  wrote:
> >  
> >> On 27/12/2021 23:20, Leo Famulari wrote:  
> >>> On Mon, Dec 27, 2021 at 10:07:17PM +0000, Paul Jewell wrote:  
> >>>> Solved this - nmtui needs to be run as root; my script which
> >>>> invoked the program didn't consider that. Changing it to run as
> >>>> sudo gives me an opportunity to enter my password, and then
> >>>> successfully setup the wifi interface details.  
> >>> Another option is to add nmtui to the list of programs that are
> >>> setuid. That way, any user on your system could configure wifi,
> >>> which may be more ergonomic.
> >>>
> >>> https://guix.gnu.org/manual/devel/en/html_node/Setuid-Programs.html
> >>>     
> >> This option did work as expected. The only additional point for
> >> anyone else coming across this post with the same issue: remember
> >> to add the
> >>
> >> #:use-module (gnu system setuid)
> >>
> >> so the setuid record is known.
> >>
> >> Thanks Leo!  
> > Uhm, I'm pretty sure NetworkManager lets any user modify networking
> > settings as long as they are in a certain group?
> > https://wiki.archlinux.org/title/NetworkManager#Set_up_PolicyKit_permissions
> >
> > At least that's how it is on postmarketOS and I'm also fairly
> > certain I never needed root access to set up WiFi under Guix
> > either, but I don't have a system at hand to verify that on.  
> 
> I did also think this, but I couldn't identify which group would let 
> this happen. I thought it would be the netdev group, but my user
> account is already a member of that group. The network group is
> unknown to the system (as in I had an error when trying to add the
> user to the supplementary group) so I added it, but it didn't have
> any effect (after rebooting). If there is another group I should be
> in, I am not sure how to find out. At the moment, the setuid approach
> seems to work OK (although I would prefer a group solution!).
> 
> I am interested in anyone else's experience!

It might be that everyone else is including some default configuration
for NetworkManager and we aren't. At the very least it should be
documented how to set it up to use groups.

CC-ing bugs-guix 


  reply	other threads:[~2021-12-30 19:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-27  7:33 nmtui - user authorisation Paul Jewell
2021-12-27 22:07 ` Paul Jewell
2021-12-27 23:20   ` Leo Famulari
2021-12-28 18:39     ` Paul Jewell
2021-12-29  0:50       ` raingloom
2021-12-29 11:04         ` Paul Jewell
2021-12-30 19:00           ` raingloom [this message]
2021-12-31 18:41             ` bug#52904: " Josselin Poiret via Bug reports for GNU Guix
2022-01-02  9:32               ` Paul Jewell
2022-01-02 11:07                 ` Josselin Poiret
2022-01-02 20:42                   ` Mekeor Melire

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=20211230200023.7aec38ae@riseup.net \
    --to=raingloom@riseup.net \
    --cc=bug-guix@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=paul@teulu.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).