[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: looking for the solution of rootless subhurd
From: |
olafBuddenhagen |
Subject: |
Re: looking for the solution of rootless subhurd |
Date: |
Fri, 9 Jan 2009 09:09:08 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
Hi,
On Sun, Jan 04, 2009 at 07:20:17PM +0000, Da Zheng wrote:
> Zheng Da wrote:
>> I just found there is the RPC proc_getallpids, so I can get all
>> processes in the main hurd and then use pid2task to get their task
>> port. I also found that pid2task only works for the tasks that belong
>> to the caller. It almost solves my problem as long as the tasks
>> created in subhurd belong to the user of subhurd in the eyes of the
>> main Hurd.
> I am afraid that it doesn't work. I mean boot cannot get all tasks in
> subhurd from the main Hurd's proc server. I guess the reason is that
> the tasks in subhurd cannot register themselves properly in the main
> Hurd's process server and the process server doesn't know who the
> tasks in subhurd belong to, and meanwhile, pid2task only works for
> the tasks that belong to the caller.
Are you saying that if a task fails to register itself with the proc
server, it can not be associated with any user, i.e. only root can kill
the task? That would be a serious security problem for all I know...
-antrik-