> > great an idea... or that useful an idea for that matter. Adding
> > some conditional code into vfs_unlink() in fs/namei.c would be great
> > 'coz that's the multiplexer for the various filesystems' unlink
> > code. It'd also make it pretty easy to turn off. You could even
> > throw in a file into proc to turn it on and off. That'd be the bomb
> > -- I'd turn it before alcohol, turn it back off when I'm sober :-)
> > If I remembered, that is...
>
> What "security concern" are you talking about? Someone asked a
> question about how copying to a file works, and I answered that. It
> was separate to the discussion, though, and has nothing to do with
> security.
>
> Note that static binaries don't matter. They will just exhibit the
> existing behaviour (delete). No security problem there.
>
> There is simply no need for an undelete/move-to-garbage-area feature
> in the kernel. It can all be done perfectly fine in userspace.
I'm not looking at this undelete feature as a neat convenient "I screwed
up" tool. I'm more looking at it as an audit tool.
--- Tani Hosokawa River Styx Internet
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/