All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Petr Baudis <pasky@suse.cz>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	akpm@osdl.org, viro@zeniv.linux.org.uk, alan@lxorguk.ukuu.org.uk,
	tytso@mit.edu, tigran@veritas.com
Subject: Re: [RFC/PATCH] revoke/frevoke system calls V2
Date: Thu, 27 Jul 2006 21:10:36 +0300	[thread overview]
Message-ID: <1154023836.7190.3.camel@ubuntu> (raw)
In-Reply-To: <20060727180634.GA28962@pasky.or.cz>

On Thu, 2006-07-27 at 20:06 +0200, Petr Baudis wrote:
> Make that setuid root or just create log file owned by you and make root
> run it.  Should be innocent enough, right?
> 
> Well, except that you can revoke the log file before the shadow file is
> opened, at which point open() probably reuses the fd and the program
> conveniently logs to /etc/shadow.

No, the fd is leaked on purpose to avoid recycling. See revoke_fds for
details.


  reply	other threads:[~2006-07-27 18:10 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 14:25 [RFC/PATCH] revoke/frevoke system calls V2 Pekka J Enberg
2006-07-27 15:07 ` Alan Cox
2006-07-27 15:33   ` Pekka Enberg
2006-07-27 16:09     ` Alan Cox
2006-07-27 16:01       ` Pekka J Enberg
2006-07-27 16:30         ` Alan Cox
2006-07-27 17:07           ` Pekka J Enberg
2006-07-27 18:27           ` Pekka Enberg
2006-07-27 16:41 ` Ulrich Drepper
2006-07-27 17:05   ` Pekka J Enberg
2006-07-27 17:13     ` Ulrich Drepper
2006-07-27 17:33       ` H. Peter Anvin
2006-07-27 17:44         ` Ulrich Drepper
2006-07-27 18:00           ` H. Peter Anvin
2006-07-27 17:33     ` Alan Cox
2006-07-27 17:33       ` O_CAREFUL flag to disable open() side effects H. Peter Anvin
2006-07-27 17:43         ` Russell King
2006-07-27 17:50         ` Ulrich Drepper
2006-07-27 18:05         ` Alan Cox
2006-07-27 18:03           ` H. Peter Anvin
2006-07-27 18:14             ` Joshua Hudson
2006-08-05 21:05       ` [RFC/PATCH] revoke/frevoke system calls V2 Pavel Machek
2006-07-27 18:06 ` Petr Baudis
2006-07-27 18:10   ` Pekka Enberg [this message]
2006-07-27 19:30     ` Horst H. von Brand
2006-07-28  3:40       ` Pekka J Enberg
2006-07-27 18:34   ` Alan Cox
2006-08-05 12:29 ` Pavel Machek
2006-08-07  5:42   ` Pekka J Enberg
2006-08-07  8:17   ` Edgar Toernig
2006-08-07  9:51     ` Pekka Enberg
2006-08-07 20:41       ` Edgar Toernig
2006-08-07 22:24         ` Chase Venters
2006-08-08 12:15           ` Alan Cox
2006-08-09  8:41             ` Edgar Toernig
2006-08-09 10:39               ` Alan Cox
2006-08-09 18:00                 ` Edgar Toernig
2006-08-09 18:36                   ` Alan Cox
2006-08-09 19:13                     ` Pekka Enberg
2006-08-09 20:08                       ` Edgar Toernig
2006-08-09 21:29                       ` Edgar Toernig
2006-08-11  7:52                   ` Helge Hafting
2006-08-07 22:52         ` David Wagner
2006-08-07 22:56           ` Daniel Jacobowitz
2006-08-07 23:12             ` Chase Venters
2006-08-08 12:16               ` Pekka Enberg
2006-08-08 16:02                 ` Kari Hurtta
2006-08-08 21:54                   ` Theodore Tso
2006-08-09  6:32                     ` Pekka Enberg
2006-08-08 12:13           ` Alan Cox
2006-08-08 12:29         ` Alan Cox
2006-08-08 12:31           ` Pekka Enberg
2006-08-08 12:57           ` Pavel Machek
2006-08-08 14:14             ` Alan Cox
2006-08-08 13:57               ` Pavel Machek
2006-08-09  8:41           ` Edgar Toernig
2006-08-09 10:42             ` Alan Cox
2006-08-09 18:00               ` Edgar Toernig
2006-08-09 18:35                 ` Alan Cox
2006-08-09 19:14                   ` Pekka Enberg

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=1154023836.7190.3.camel@ubuntu \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=tigran@veritas.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.