All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Philippe Gerum <rpm@xenomai.org>, xenomai@xenomai.org
Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : sysregd: Install as suid
Date: Mon, 12 Jan 2015 15:00:59 +0100	[thread overview]
Message-ID: <54B3D39B.7040900@siemens.com> (raw)
In-Reply-To: <54B3C134.5020101@siemens.com>

On 2015-01-12 13:42, Jan Kiszka wrote:
> On 2015-01-12 11:34, Philippe Gerum wrote:
>> On 01/08/2015 05:30 PM, git repository hosting wrote:
>>> Module: xenomai-jki
>>> Branch: for-forge
>>> Commit: 7d56f2b19f987069ef0025f9ce5f8cc52781f340
>>> URL:    http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=7d56f2b19f987069ef0025f9ce5f8cc52781f340
>>>
>>> Author: Jan Kiszka <jan.kiszka@siemens.com>
>>> Date:   Thu Jan  8 14:30:52 2015 +0100
>>>
>>> sysregd: Install as suid
>>>
>>> sysregd has to run with root privileges in order to be able to clean up
>>> the mounts of unprivileged users.
>>>
>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>>
>>
>> This one assumes root id on "make install", which is not a prerequisite
>> for installing a Mercury setup. This leads to sysregd losing root
>> privileges on execution, which contradicts the purpose.
>>
>> We need sudo detection and use for this, just like we do in the top
>> level Makefile for creating /dev entries.
> 
> OK.

Is there a way to maintain that sudo test code only in one place? I'm
currently not finding an obvious one.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2015-01-12 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Y9Fya-0004Me-Ao@sd-51317.xenomai.org>
2015-01-12 10:34 ` [Xenomai] [Xenomai-git] Jan Kiszka : sysregd: Install as suid Philippe Gerum
2015-01-12 12:42   ` Jan Kiszka
2015-01-12 14:00     ` Jan Kiszka [this message]
2015-01-12 14:11       ` Jan Kiszka

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=54B3D39B.7040900@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=rpm@xenomai.org \
    --cc=xenomai@xenomai.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 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.