mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Coywolf Qi Hunt <coywolf@gmail.com>
Cc: Peter Williams <pwil3058@bigpond.net.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	torvalds@osdl.org, sam@ravnborg.org
Subject: Re: [q] make modules_install as non-root?
Date: Fri, 02 Dec 2005 11:21:46 -0300	[thread overview]
Message-ID: <200512021421.jB2ELkJw013434@pincoya.inf.utfsm.cl> (raw)
In-Reply-To: Message from Coywolf Qi Hunt <coywolf@gmail.com>  of "Fri, 02 Dec 2005 10:59:11 +0800." <2cd57c900512011859v7f0db82fg@mail.gmail.com>

Coywolf Qi Hunt <coywolf@gmail.com> wrote:
> 2005/12/2, Peter Williams <pwil3058@bigpond.net.au>:

[...]

> > Personally, I just use "sudo make install" or "sudo make
> > modules_install" to do installations as an ordinary user.  No need for
> > special scripts or modifications to the build procedure.

> That's rather insecure. You have to add /usr/bin/make in your sudoers,
> then an malicious Makefile could do harm. I'm being paranoid. But we
> all are since we avoid to use root.

Oh, come on. If somebody can mess with your kernel sources, you are toast
anyway. No need to doctor a Makefile for that at all.
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

  parent reply	other threads:[~2005-12-02 15:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02  2:23 Coywolf Qi Hunt
2005-12-02  2:46 ` Peter Williams
2005-12-02  2:59   ` Coywolf Qi Hunt
2005-12-02  3:04     ` Peter Williams
2005-12-02 14:21     ` Horst von Brand [this message]
2005-12-02  3:11 ` Keith Owens

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=200512021421.jB2ELkJw013434@pincoya.inf.utfsm.cl \
    --to=vonbrand@inf.utfsm.cl \
    --cc=coywolf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pwil3058@bigpond.net.au \
    --cc=sam@ravnborg.org \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®