Messages in this thread | | | From | "Clayton Weaver" <> | Date | Fri, 11 Apr 2003 12:11:18 -0500 | Subject | Re: [PATCH] new syscall: flink |
| |
> [David Wagner, "should fail closed", ie with the capability to flink()to any given open file descriptor disabled by default]
Ok, that's reasonable. I was imagining that guessing when you need to enable it for an open fd that is going to be inherited by someone else's code that may not even have been written yet is rather a vague proposition, while guessing when you need to disable it regardless of what the code that you pass it to does is likely to be all too clear and made much of in online discussions.
But some application author not noticing that a potential flink() vulnerability is there at all will perhaps be the more common failure scenario(so I yield the point).
flink() does seem a useful tool that I've wanted in the past (for reasons similar to the linker example) if one could get around the implicit security risk of a naive implementation.
Regards,
Clayton Weaver <mailto: cgweav@email.com>
-- _______________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |