Re: [IAEP] [Sugar-devel] A security vs. functionality question

2009-08-06 Thread Lucian Branescu
Could you let the invited user in a chroot by default and only allow full access if the inviting user explicitly allows it? 2009/8/6 Benjamin M. Schwartz bmsch...@fas.harvard.edu: Gary C Martin wrote: How are two (or more!) remote individuals expected to co-operate and share the same command

Re: [IAEP] [Sugar-devel] A security vs. functionality question

2009-08-06 Thread Benjamin M. Schwartz
Lucian Branescu wrote: Could you let the invited user in a chroot by default and only allow full access if the inviting user explicitly allows it? 1. What sort of interface do you have in mind? What is more explicit than Share with: My Neighborhood? 2. Why a chroot, and not Rainbow? 3. How

Re: [IAEP] [Sugar-devel] A security vs. functionality question

2009-08-06 Thread Lucian Branescu
Share with: My Neighborhood is too broad to allow full access. But Share with: John should be enough to assume that you trust John. Or instead have a separate option Share with: John (full acces). A chroot because afaik rainbow doesn't really work outside the XO distro My impression may be wrong,

Re: [IAEP] [Sugar-devel] A security vs. functionality question

2009-08-06 Thread Benjamin M. Schwartz
Lucian Branescu wrote: Share with: My Neighborhood is too broad to allow full access. But Share with: John should be enough to assume that you trust John. Or instead have a separate option Share with: John (full acces). Sugar does support direct Invitations for private sharing. I like the

Re: [IAEP] [Sugar-devel] A security vs. functionality question

2009-08-06 Thread Michael Stone
Lucian, Ben: Here are a bunch of reactions. Apologies for the delay. :) Michael Lucian Branescu wrote: A chroot because afaik rainbow doesn't really work outside the XO distro My impression may be wrong, though. Would you mind taking a look at http://wiki.laptop.org/go/Rainbow for