From: "M.L.PrasannaK.R." <mlpkr@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: fsuid0 caps
Date: Wed, 4 Sep 2002 14:11:18 -0700 (PDT) [thread overview]
Message-ID: <20020904211118.37877.qmail@web13808.mail.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
In reply to
ttp://www.uwsg.iu.edu/hypermail/linux/kernel/0204.3/0380.html
This is documentation error. There is also a break in default
semantics of uid0 that needs to be fixed.
It is not a security hole as it results in the reduced capabilities
rather than in the increased capabilities.
setresuid(x,x,-1) clears effective caps.
setfsuid(0) rstores CAP_FS_MASK effective caps.
setresuid(-1,-1,x) clears both effective and permitted caps.
Both fs and non fs caps are lost.
This results in uid0 with no capabilties and no way of
restoring them. If this is valid issue, something like
the following patch fixes it.
Thanks,
MLPKR.
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
[-- Attachment #2: fsuid_caps.patch --]
[-- Type: application/x-unknown, Size: 1703 bytes --]
reply other threads:[~2002-09-04 21:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020904211118.37877.qmail@web13808.mail.yahoo.com \
--to=mlpkr@yahoo.com \
--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
all inboxes | Powered by JetHome®