From: kuznet@ms2.inr.ac.ru
To: alan@lxorguk.ukuu.org.uk (Alan Cox)
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: Local root exploit with kmod and modutils > 2.1.121
Date: Thu, 16 Nov 2000 20:32:19 +0300 (MSK) [thread overview]
Message-ID: <200011161732.UAA03398@ms2.inr.ac.ru> (raw)
In-Reply-To: <E13wShQ-000860-00@the-village.bc.nu> from "Alan Cox" at Nov 16, 0 05:19:45 pm
Hello!
> Only the caller knows if the data is tainted. Thus only the caller can decide
Sorry? What data? What to decide?
Device name of &|&|&|&|&|& is absolutely legal, nicely loking name.
dev.c _wants_ to load such device and it is problem of kmod,
if it is not able to make this.
It is the first. And the second: each user is allowed to refer to this device.
And it is problem of module to allow to load corresponding module or not
to allow this.
It means that test for CAP_SYS_MODULE is illegal, moving pure policy
issue to improper place.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-16 18:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0011131915240.19775-100000@ferret.lmh.ox.ac.uk>
2000-11-13 23:11 ` Local root exploit with kmod and modutils > 2.1.121 Keith Owens
2000-11-16 16:04 ` Alan Cox
2000-11-16 17:05 ` kuznet
2000-11-16 17:19 ` Alan Cox
2000-11-16 17:32 ` kuznet [this message]
2000-11-16 18:24 ` Alan Cox
2000-11-16 18:56 ` kuznet
2000-11-16 19:08 ` [PATCH] " Xavier Bestel
2000-11-16 20:24 ` Keith Owens
2000-11-16 21:45 ` Alan Cox
2000-11-14 20:31 Adam J. Richter
2000-11-14 22:50 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2000-11-13 10:57 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=200011161732.UAA03398@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox