From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: RAMON_GARCIA_F <RAMON_GARCIA_F@terra.es>, linux-kernel@vger.kernel.org
Subject: Re: Suggestion for a new system call: convert file handle to a cookie for transfering file handles between processes.)
Date: Mon, 21 Jul 2003 21:31:44 +0200 [thread overview]
Message-ID: <20030721213144.O639@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20030721172656.GA32597@delft.aura.cs.cmu.edu>; from jaharkes@cs.cmu.edu on Mon, Jul 21, 2003 at 01:27:06PM -0400
On Mon, Jul 21, 2003 at 01:27:06PM -0400, Jan Harkes wrote:
> - Refcounting issues, a rogue application can quickle use up kernel
> resources by requesting thousands of cookies, he isn't even limited by
> per-process resource limits, as it is possible to open a file, grab a
> cookie, and close the file. The only 'solution' you have is a timeout
> on the cookie, possibly this could be extended by some scheme where
> cookies are dropped more agressivly. But any such solution will either
> not be sufficient to protect the system from resource exhaustion or
> provide the opportunity for denial of service attacks.
Best of all: How big you make the number, doesn't matter: You can
always guess such numbers as a local attacker. If not now, then
in some years (want to recompile all existing applications then?).
cmsg(SCM_RIGHTS) is the much better solution, if you really have
processes, which are neither a sibling nor a parent/child
relationship.
And it's also ugly enough ;-)
Regards
Ingo Oeser
next prev parent reply other threads:[~2003-07-22 2:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 17:04 RAMON_GARCIA_F
2003-07-21 17:27 ` Jan Harkes
2003-07-21 19:31 ` Ingo Oeser [this message]
2003-07-21 19:06 RAMON_GARCIA_F
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=20030721213144.O639@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=RAMON_GARCIA_F@terra.es \
--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®