[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: task info cap access
From: |
Marcus Brinkmann |
Subject: |
Re: task info cap access |
Date: |
Fri, 29 Aug 2003 19:48:18 +0200 |
User-agent: |
Mutt/1.5.4i |
On Fri, Aug 29, 2003 at 05:51:06PM +0200, Ludovic Courtès wrote:
> Hi,
>
> I'm not sure I understand capabilities well enough. From my
> understanding, there is no difference between capabilities given out by
> OS servers and CORBA's IOR ("Interchange Object Reference" IIRC): a
> capability is some sort of an unforgeable data structure representing a
> remote object/resource. Is this correct? If so, then it might be
> useful to look at how ORBs deal with IORs.
I think we had this mentioned before. CORBA seems to use long random
numbers, in string form. First, they are forgeable, of course. Well, it's
not practical to guess them. But still, there is a non-zero chance of being
able to guess it. For example, it might be difficult to create good random
numbers to create such IORs, as good random is always in short supply on any
system. More important, if they are secure they are long, and if they are
long, and you have to carry them in every single message you send, you are
killing off a huge chunk of L4's performance advantage. The IOR would often
be larger than the message itself.
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' GNU http://www.gnu.org address@hidden
Marcus Brinkmann The Hurd http://www.gnu.org/software/hurd/
address@hidden
http://www.marcus-brinkmann.de/