[Sugar-devel] Parental controls (UPDATE)

Ryan Cunningham rvskmbrly3 at gmail.com
Wed Apr 23 20:38:06 EDT 2014


One could simply disable access to the Terminal activity. He could also disable 'getty' on all virtual terminals not being used for X11 (how to do so depends on his flavor of 'init' and is outside the scope of this feature). For Ubuntu, additional steps are needed: he would also disable the "Resume normal boot" entry in the recovery menu and configure a password for the root account.

-- 
Sent from my iPad

> On Apr 23, 2014, at 5:10 PM, forster at ozonline.com.au wrote:
> 
> Hi
> 
> You say "For this  GUI to reach a wider user base, parental controls are therefore  needed."
> 
> Can you please expand on this. Why are these controls needed? In which circumstances would they be enabled? Which releases would be controlled?
> 
> Historically, Sugar and OLPC have been based on a philosophy of empowering the user. "Hacking" has been facilitated by Sugar as default and only disabled if at the specific request of a deployment.
> 
> The security you propose could possibly be bypassed by reflashing with another image or by hacking the Browse Activity?
> 
> Tony
> 
> 


More information about the Sugar-devel mailing list