From: Andrew Morton <akpm@osdl.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add user taint flag
Date: Mon, 22 May 2006 03:36:44 -0700 [thread overview]
Message-ID: <20060522033644.26d47a00.akpm@osdl.org> (raw)
In-Reply-To: <E1FhwyO-0001YQ-O1@candygram.thunk.org>
"Theodore Ts'o" <tytso@mit.edu> wrote:
>
>
> Allow taint flags to be set from userspace by writing to
> /proc/sys/kernel/tainted, and add a new taint flag, TAINT_USER, to be
> used when userspace is potentially doing something naughty that might
> compromise the kernel.
What sort of userspace actions are you thinking of here?
And how is other userspace to detect what the naughty userspace is doing?
Someone's done something and you're not telling us what it was ;)
>
> ...
>
> +/*
> + * Taint values can only be increased
> + */
> +int proc_dointvec_taint(ctl_table *table, int write, struct file *filp,
> + void __user *buffer, size_t *lenp, loff_t *ppos)
> +{
> + int op;
> +
> + if (!capable(CAP_SYS_ADMIN)) {
> + return -EPERM;
> + }
Aren't the /proc file permissions sufficient?
next prev parent reply other threads:[~2006-05-22 10:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 23:04 Theodore Ts'o
2006-05-22 10:36 ` Andrew Morton [this message]
2006-05-22 18:33 ` Theodore Tso
2006-05-22 23:49 ` Nick Piggin
2006-05-24 13:43 ` Stefan Seyfried
2006-05-22 12:17 ` Stephen C. Tweedie
2006-05-22 14:14 ` Arjan van de Ven
2006-05-22 14:35 ` Alan Cox
2006-05-22 14:29 ` Valdis.Kletnieks
2006-05-22 18:56 ` Jan Engelhardt
2006-05-22 14:37 ` Arjan van de Ven
2006-05-23 1:11 ` Theodore Tso
2006-05-22 15:48 ` Randy.Dunlap
2006-05-23 18:45 ` Greg KH
2006-05-24 13:39 ` Theodore Tso
2006-05-24 13:55 ` Dave Jones
2006-05-24 14:15 ` Dave Jones
2006-05-25 15:01 ` Greg KH
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=20060522033644.26d47a00.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
Powered by JetHome