-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Al Viro wrote: > So which code is supposed to do that open/write in your example? Library? > Unmodified application? Application specifically modified to make *that* > open() randomized?
Why should that matter? All of the above. Any piece of code can of course choose to not be safe but it should have the opportunity to be, too. Currently that's not the case. With an O_NONSEQFD flag to open it would be trivial to change any code. Or one can introduce a new set of userlevel interfaces to create and write new files which then can do even more. In whatever way you look at it, there currently is a problem which cannot be solved except with truly horrible, horrible hack (open N descriptors and randomly select one to use; yep, horrible, I said so). - -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGatS62ijCOnn/RHQRAqcfAJ9vMc6GUFxlgxOZ9rhAcTV9N95kUACguUpq ER8Y64pIp80NHiMHXwMxxK0= =ytei -----END PGP SIGNATURE----- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
