"secure" file flag?
Pawel Jakub Dawidek
nick at garage.freebsd.pl
Fri Nov 21 04:45:26 PST 2003
On Fri, Nov 21, 2003 at 12:41:05PM +0100, Dag-Erling Sm?rgrav wrote:
+> > If this operation is able to fail (and of course it is) it should block
+> > on unlink(2).
+> FreeBSD is not DOS; unlink(2) does not actually remove the file. It
+> is removed by the filesystem if the link count is zero when the vnode
+> is released, which may be immediately after the unlink(2) call, or an
+> indefinite amount of time later if the file was open at the time.
I'm aware of this, but what we want to think over here is something like
in-kernel 'rm -P'. So file will be overwriten even if it is opened
and/or link count is grater than 0. That's why allowing link(2) operation
for such files don't make much sens (the problem exists when there
are hardlinks before "secure" flag is set).
Pawel Jakub Dawidek pawel at dawidek.net
UNIX Systems Programmer/Administrator http://garage.freebsd.pl
Am I Evil? Yes, I Am! http://cerber.sourceforge.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 305 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20031121/e39ec75c/attachment.bin
More information about the freebsd-hackers