On Sat, Aug 09, 2003 at 05:33:29PM -0400, Roland McGrath wrote:The concern I have about this patch per se is proc calling thread_resume on a random port from the user. This is at least a DoS opportunity. It also points to a more general problem rpctrace has--servers make comparisons between ports from the user (rpctrace) and ports outside rpctrace's sphere of interposition. I bet "rpctrace ln foo bar" (dir_link) gets EXDEV too.
Shall I revert the patch?
proc also uses the task port given by rpctrace. So one can write a program that passes fake task port to proc, and when proc tries to handle the fake process in some way, the whole proc server will hang because it is single-threaded. Isn't it principally like the thread_resume case?
Regards -- Ognyan Kulev <[EMAIL PROTECTED],fsa-bg.org}> 7D9F 66E6 68B7 A62B 0FCF EB04 80BF 3A8C A252 9782
_______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
