[Sugar-devel] Parental controls (UPDATE)

[Ryan Cunningham]

-- 
Sent from my iPad

> On Apr 23, 2014, at 5:46 PM, James Cameron <quozl at laptop.org> wrote:
> 
> Any access control specific to activities would have to keep a list of
> activities that are controlled, and the list would have to survive
> over an activity deinstall reinstall cycle.  An activity could be
> renamed to avoid this control.  We have no authentication of
> activities on which to base these controls.  We have forked activities
> with similar function but different name; e.g. Turtle Blocks vs Turtle
> Bots.

This access control list is a separate entity from any activity---it being stored in "~/.sugar" when activities are stored in "~/Activities" or "/usr/share/sugar/activities"---and the forked activity could be added to the access control list as needed.

> 
> -- 
> James Cameron
> http://quozl.linux.org.au/
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel