all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: ng0 <ng0@pragmatique.xyz>
Cc: 27311@debbugs.gnu.org
Subject: bug#27311: Acknowledgement (Enlightenment: 'cpufreq binary needs suid or has to be owned by root')
Date: Wed, 21 Jun 2017 10:00:14 +0200	[thread overview]
Message-ID: <87mv913h4h.fsf@elephly.net> (raw)
In-Reply-To: <20170611172511.rgratbogpqv5aop3@abyayala>


ng0 <ng0@pragmatique.xyz> writes:

> Nix solved this particular issue (cpufreq) with a hack.
> It's okay for me, but do some of you agree with applying this:
>
>   # this is a hack and without this cpufreq module is not working. does the following:
>   #   1. moves the "freqset" binary to "e_freqset",
>   #   2. linkes "e_freqset" to enlightenment/bin so that,
>   #   3. wrappers.setuid detects it and places wrappers in /run/wrappers/bin/e_freqset,
>   #   4. and finally, links /run/wrappers/bin/e_freqset to original destination where enlightenment wants it
>   postInstall = ''
>     export CPUFREQ_DIRPATH=`readlink -f $out/lib/enlightenment/modules/cpufreq/linux-gnu-*`;
>     mv $CPUFREQ_DIRPATH/freqset $CPUFREQ_DIRPATH/e_freqset
>     ln -sv $CPUFREQ_DIRPATH/e_freqset $out/bin/e_freqset
>     ln -sv /run/wrappers/bin/e_freqset $CPUFREQ_DIRPATH/freqset
>   '';

No, we shouldn’t apply this hack.  Setuid binaries are declared
separately in the operating system configuration.  See section 6.2.8
Setuid Programs in the manual.

Packages cannot declare setuid binaries.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-06-21  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-10 15:03 bug#27311: Enlightenment: 'cpufreq binary needs suid or has to be owned by root' ng0
     [not found] ` <handler.27311.B.149710706324063.ack@debbugs.gnu.org>
2017-06-11 16:35   ` bug#27311: Acknowledgement (Enlightenment: 'cpufreq binary needs suid or has to be owned by root') ng0
2017-06-11 17:25     ` ng0
2017-06-21  8:00       ` Ricardo Wurmus [this message]
2018-08-05  9:44         ` Efraim Flashner

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=87mv913h4h.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=27311@debbugs.gnu.org \
    --cc=ng0@pragmatique.xyz \
    /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.