unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Allan Webber <cwebber@dustycloud.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, sbaugh@catern.com
Subject: Re: Providing an alternative to setuid in GuixSD
Date: Wed, 26 Oct 2016 12:52:31 -0500	[thread overview]
Message-ID: <87zilr6lr4.fsf@dustycloud.org> (raw)
In-Reply-To: <878ttbti19.fsf@gnu.org>

Ludovic Courtès writes:

> SSH is a complex protocol and its implementations are complex too.  I
> would find it unreasonable to replace ‘su’ and ‘sudo’ with something
> this complex, that goes through the TCP/IP stack, etc.

I agree.  We could maybe have a pseudo-sudo service that is built just
for this purpose though... let's call it "psudo". ;)  Thinking out loud:

So, you're running psudo, and this thing maybe accepts connections over
something more secure, *maybe* unix domain sockets... so restrict group
access to the socket to users in the "psudo" group.

From there, maybe it could require PAM authentication while entering the
root password, or something.

It feels hard to know how psudo could "know" what user is accessing the
socket... I don't think that information is made available, right?
Maybe I'm wrong!  I guess postgres and etc do similar things?

Fun idea to think about anyway :)

  parent reply	other threads:[~2016-10-26 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-23 15:17 Providing an alternative to setuid in GuixSD sbaugh
2016-10-24  0:09 ` Chris Marusich
2016-10-24 22:01   ` sbaugh
2016-10-26 12:24 ` Ludovic Courtès
2016-10-26 14:40   ` sbaugh
2016-10-28 13:34     ` Ludovic Courtès
2016-10-29 21:41       ` sbaugh
2016-10-26 17:52   ` Christopher Allan Webber [this message]
2016-10-26 18:34     ` sbaugh

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=87zilr6lr4.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=sbaugh@catern.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).