From: Marius Bakke <mbakke@fastmail.com>
To: dian_cecht@zoho.com, help-guix@gnu.org
Subject: Re: How to setuid X.org?
Date: Mon, 20 Mar 2017 07:48:01 +0100 [thread overview]
Message-ID: <877f3k78bi.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170319200255.5ef60556@khaalida>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
dian_cecht@zoho.com writes:
> Hello,
>
> I have tried several times to get X.org (/bin/X, specifically)
> setuid for obvious reasons. However, I can't find any examples of usage
> and attempting to follow the infopages has led to a bunch of different
> errors and failures (and rather useless error messages). I currently
> don't have any useful logs of what I tried and the output (it was on a
> LiveUSB I'm using for testing purposes), but I'm not wanting to use
> %desktop-services (or other service packs, for that matter), which has
> already been suggested.
>
> Can someone either A) improve the documents for setuid programs (and
> gexps) with some practical examples, or B) provide me with a (hopefully
> working) snippet to add to the config?
Setuid programs are documented here:
https://www.gnu.org/software/guix/manual/guix.html#Setuid-Programs
Following the "passwd" example, making "X" setuid root would be declared
like this:
(operating-system
[...]
(setuid-programs
(cons #~(string-append #$xorg-server "/bin/X")
%setuid-programs))
It's not clear to me how to improve this since it's very similar to how
other defaults are overridden. Any suggestions?
TIA!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-03-20 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 3:02 How to setuid X.org? dian_cecht
2017-03-20 6:48 ` Marius Bakke [this message]
2017-03-20 8:50 ` Ludovic Courtès
2017-03-21 15:11 ` dian_cecht
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=877f3k78bi.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=dian_cecht@zoho.com \
--cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.