> 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.
a) proc is not single-threaded b) proc does not send messages to task ports supplied by users (a bogus one gets you ESRCH from proc_child/proc_reassign) _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
