From: Tim Waugh <twaugh@redhat.com>
To: kees <kees@schoen.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] exec_via_sudo
Date: Tue, 10 Apr 2001 12:16:22 +0100 [thread overview]
Message-ID: <20010410121622.H1136@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0104101251210.6726-100000@schoen3.schoen.nl>
In-Reply-To: <Pine.LNX.4.21.0104101251210.6726-100000@schoen3.schoen.nl>; from kees@schoen.nl on Tue, Apr 10, 2001 at 12:55:29PM +0200
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On Tue, Apr 10, 2001 at 12:55:29PM +0200, kees wrote:
> Unix/Linux have a lot of daemons that have to run as root because they
> need to acces some specific data or run special programs. They are
> vulnerable as we learn.
> Is there any way to have something like an exec call that is
> subject to a sudo like permission system? That would run the daemons
> as a normal user but allow only for specific functions i.e. NOT A SHELL.
Yeah, exec sudo.
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-04-10 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 10:55 [RFC] exec_via_sudo kees
2001-04-10 11:16 ` Tim Waugh [this message]
2001-04-10 11:36 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2001-04-10 17:04 Jesse Pollard
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=20010410121622.H1136@redhat.com \
--to=twaugh@redhat.com \
--cc=kees@schoen.nl \
--cc=linux-kernel@vger.kernel.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.