XO identity shared via Browse

Tomeu Vizoso tomeu at sugarlabs.org
Fri Dec 5 11:56:55 EST 2008


On Fri, Dec 5, 2008 at 5:46 PM, Greg Smith <gregsmitholpc at gmail.com> wrote:
> Hi Luke,
>
> If you're interested in Sugar on XO, I believe that Tomeu et al want you
> on devel... Anyway I'll try to copy you on this thread.

Well, as long as there's a chance what is discussed here will interest
Sugar on other platforms, I think you are welcome to cc sugar-devel.

I personally don't see any problem with cc'ing both lists in case of
doubt, olpc and sugar are very closely related as of today.

Tomeu

> It would be useful to have a generic solution which works with many
> types of server software and many network configurations.
>
> However, this is where I need to separate "must have" from "nice to have".
>
> We must allow the XS to know which XO it is talking to when there is an
> XS and XO on the same protected network (AKA XS doing NAT and acting as
> gateway to Internet).
>
> I can't wait for the "nice to have" piece if there is no agreement on
> technical implementation. I want the "must have" piece by March, no
> matter what.
>
> I'll take both too but I wont settle for none of the above :-)
>
> Thanks,
>
> Greg S
>
> Luke Faraone wrote:
>> On Thu, Dec 4, 2008 at 19:17, Greg Smith <gregsmitholpc at gmail.com> wrote:
>>
>>> I'm copying in Devel and will drop the sugar list on further replies
>>> (hope that's the right netiquette in this case...).
>>
>> (note: I'm not on devel, so please keep me CC'd)
>>
>>
>>>  > security)   who are the principals?
>>>  >   what are their goals?
>>>  >   what attacks concern us?
>>>
>>> GS - In general I don't want any other devices to be able to appear to
>>> be the XO. We can assume that the XS <-> XO is a secure network not
>>> visible to the outside workd (whether that is true in practice is
>>> another story). So I moved the encryption and stringent security
>>> requirements to the optional case where the XO is talking to a non-XS
>>> server.
>>>
>>
>> I'd rather not make that assumption. Some schools may not have a _local_
>> school server (even dispite our best wishes) or a student may want to access
>> the server from a non-local connection. The XS, IMHO, should support the
>> "road warrior" use case (at least for post-registration)
>>
>>
>> -lf
>>
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>



More information about the Devel mailing list