From: "Zach, Yoav" <yoav.zach@intel.com>
To: <insecure@mail.od.ua>
Cc: <akpm@osdl.org>, <torvalds@osdl.org>, <linux-kernel@vger.kernel.org>
Subject: RE: Re: Re: [PATCH]: non-readable binaries - binfmt_misc 2.6.0-test4
Date: Thu, 4 Sep 2003 09:53:44 +0300 [thread overview]
Message-ID: <2C83850C013A2540861D03054B478C0601CF64F6@hasmsx403.iil.intel.com> (raw)
> --- insecure <insecure@mail.od.ua> wrote:
>
> > If the binary resides on a NFS drive ( which
> > is a very common practice )
> > then the suid-wrapper solution will not work
> > because root permissions
> > are squashed on the remote drive.
>
>
> This is a NFS promlem. Do not work around it by
> adding crap elsewhere.
> NFS has to get a decent user auth/crypto features.
> I did not try it yet, but NFSv4 will address that.
> --
This is not a workaround - it's a solution for systems
that use the unix user identification mechanism.
Considering the conservative nature of system-administrators,
this mechanism will still be in use for quite a while.
Thanks,
Yoav.
next reply other threads:[~2003-09-04 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 6:53 Zach, Yoav [this message]
2003-09-04 21:28 ` Re: Re: [PATCH]: non-readable binaries - binfmt_misc 2.6.0-test4 insecure
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=2C83850C013A2540861D03054B478C0601CF64F6@hasmsx403.iil.intel.com \
--to=yoav.zach@intel.com \
--cc=akpm@osdl.org \
--cc=insecure@mail.od.ua \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).