lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9988.1253899252@turing-police.cc.vt.edu>
Date:	Fri, 25 Sep 2009 13:20:52 -0400
From:	Valdis.Kletnieks@...edu
To:	"Dr. David Alan Gilbert" <linux@...blig.org>
Cc:	Miklos Szeredi <miklos@...redi.hu>,
	Andreas Gruenbacher <agruen@...e.de>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] vfs: new O_NODE open flag

On Fri, 25 Sep 2009 13:37:47 BST, "Dr. David Alan Gilbert" said:

> Given an fd opened in this way is it possible to reopen it normally and
> be guarenteed to get the same object?

It's not possible even without this flag. Consider:

        fd1 = open("/tmp/foo",flags);
        rc = rename("/tmp/foo","/tmp/bar");
        fd2 = open("/tmp/foo",flags);

Or were you asking if *absent that sort of tomfoolery* if it would work?

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ