public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mbuesch@freenet.de>
To: Jakob Lell <jlell@JakobLell.de>
Cc: root@chaos.analogic.com, linux-kernel@vger.kernel.org
Subject: Re: hard links create local DoS vulnerability and security problems
Date: Mon, 24 Nov 2003 19:21:48 +0100	[thread overview]
Message-ID: <200311241921.50001.mbuesch@freenet.de> (raw)
In-Reply-To: <200311241857.41324.jlell@JakobLell.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 24 November 2003 18:57, Jakob Lell wrote:
> > > To solve the problem, the kernel shouldn't allow users to create hard
> > > links to
> > > files belonging to someone else.
> >
> > No. Users must be able to create hard links to files that belong
> > to somebody else if they are readable. It's a requirement.
>
> If this is REALLY neccessary, it might be possible to prevent hard links to
> setuid binaries.

What about _not_ modifying the mainstream-kernel behaviour,
but adding an option, to make users unable to create such hard-links,
to selinux and/or grsec?

> Regards
>  Jakob

- -- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/wkw8oxoigfggmSgRArwLAJ47CAW90QtuEK+PNAlpzDf3ZBmohgCeKaGT
YKUZQRAYYnszq90a34KmH6U=
=EUOO
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2003-11-24 18:21 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 16:36 hard links create local DoS vulnerability and security problems Jakob Lell
2003-11-24 17:05 ` Måns Rullgård
2003-11-24 20:42   ` Mike Fedyk
2003-11-24 17:14 ` Richard B. Johnson
2003-11-24 17:35   ` Jamie Lokier
2003-11-24 18:57     ` aic7xxx loading oops in 2.6.0-test10 Alexander Nyberg
2003-11-24 20:03       ` Ken Witherow
     [not found]         ` <Pine.LNX.4.58.0311241524310.1245@morpheus>
2003-11-24 20:49           ` Ken Witherow
2003-11-24 23:42             ` Dick Streefland
2003-11-25  3:16     ` hard links create local DoS vulnerability and security problems Matthias Andree
2003-11-25 14:48     ` Jan Kara
2003-11-25 15:27       ` Jakob Lell
2003-11-24 17:37   ` Rudo Thomas
2003-11-24 18:10     ` Richard B. Johnson
2003-11-24 18:22       ` Valdis.Kletnieks
2003-11-24 22:17       ` [OT] " Rudo Thomas
2003-11-24 17:57   ` Jakob Lell
2003-11-24 18:08     ` splite
2003-11-24 18:13       ` Richard B. Johnson
2003-11-24 18:24         ` Jakob Lell
2003-11-24 23:57         ` bill davidsen
2003-11-24 18:18       ` Jakob Lell
2003-11-24 18:29         ` Valdis.Kletnieks
2003-11-24 19:25           ` hard links create local DoS vulnerability and security proble Mathieu Chouquet-Stringer
2003-11-24 20:00             ` Valdis.Kletnieks
2003-11-24 20:02               ` Mathieu Chouquet-Stringer
2003-11-24 20:22             ` H. Peter Anvin
2003-11-24 18:21     ` Michael Buesch [this message]
2003-11-24 18:35       ` hard links create local DoS vulnerability and security problems Jakob Lell
2003-11-24 18:53       ` Chris Wright
2003-11-25  0:04         ` bill davidsen
2003-11-25 13:54     ` Jesse Pollard
2003-11-24 23:50 ` bill davidsen
2003-11-25  0:22   ` Mike Fedyk
2003-11-25  0:35   ` Chris Wright
2003-11-25  8:15     ` Amon Ott
2003-11-25 16:11     ` Bill Davidsen
2003-11-25 11:26 ` Gianni Tedesco
     [not found] <fa.hevpbbs.u5q2r6@ifi.uio.no>
     [not found] ` <fa.l1quqni.v405hu@ifi.uio.no>
2003-11-24 20:54   ` Andy Lutomirski
2003-11-24 21:16     ` Linus Torvalds
2003-11-24 23:28       ` Ricky Beam
2003-11-24 22:04     ` John Bradford
2003-11-24 22:12       ` Måns Rullgård
2003-11-25 12:10         ` John Bradford
2003-11-25 12:18           ` Måns Rullgård
2003-11-25 13:12             ` John Bradford

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=200311241921.50001.mbuesch@freenet.de \
    --to=mbuesch@freenet.de \
    --cc=jlell@JakobLell.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    /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