linux-kernel - Re: O_NOLINK for open()

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: <20070913091345.GB5125@atrey.karlin.mff.cuni.cz>
Date:	Thu, 13 Sep 2007 11:13:45 +0200
From:	Jan Kara <jack@...e.cz>
To:	Bodo Eggert <7eggert@....de>
Cc:	Brent Casavant <bcasavan@....com>, linux-kernel@...r.kernel.org
Subject: Re: O_NOLINK for open()

> > However, it occurs to me that this problem goes away if there were
> > a method create a file in an unlinked state to begin with.  However
> > there does not appear to be any such mechanism in Linux's open()
> > interface.
> 
> Having no window for creating stale temp files is nice to have. We only
> need a clever fool to implement it.-) But since it's hard to get killed
> just in the right moment for having a stale temp file, there is very low
> interest for this feature.
  I don't think this is a problem. The file is simply created with link
count 0. As soon as the process closes the file, it gets deleted. So
there would be no stale files... Or did you mean anything else?

								Honza
-- 
Jan Kara <jack@...e.cz>
SuSE CR Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/