Re: Oaf default build...

[Maciej Stachowiak <mjs eazel com>]

Miguel de Icaza <miguel@helixcode.com> writes:

> 
> Anyways, what Elliot suggested was to encode the cookie in the object
> reference so that it would include the cookie in there.  This would
> enable us to just use object references: if you get the object
> reference by any mean, you would have access to the object.
> 
> Object references look like this (I have no docs here, so this is just
> what I pulled out of my butt):
> 
> 	somehost.com:5434/RootPOA/MyObject:1.0
> 
> So we would change them to be:
> 
> 	somehost.com:5434/RootPOA/asldkfaslyqewksdlifuyakhjfasdif/MyObject:1.0
> 
> Please notice that we are handling authentication: not a secure
> transport, but this is the minimal we need for having a secure
> desktop in which remote people cant invoke methods in our objects.

Is this solution implemented now? And if so, does that resolve the
security concerns?

 - Maciej