<div dir="ltr"><br><br><div class="gmail_quote">On Wed, Oct 1, 2008 at 8:37 AM, Caroline Meeks <span dir="ltr"><<a href="mailto:caroline@solutiongrove.com">caroline@solutiongrove.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr">Hi Jonas and Alan,<br><br>I agree with your thoughts here. Certainly the distribution we use should not make it easy to see the host computer's hard-drive.<br></div></blockquote><div><br>It is pretty straight forward to modify the CD/USB login menu to remove the install options and leave only the run live option.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><br>A harder problem is someone booting up with a different boot USB/CD. Most of the school computers I have met already allow boot by CD so that risk is already there.</div>
</blockquote><div><br>Yes, this is not a Sugar specific issue. If the computer already allows boot by CD, the hacking tool of choice for second graders everywhere will not be Sugar.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr"> However, it would be good to think about how we can minimize the risk to the network.<br>
</div></blockquote><div><br>This is going to be an issue. When we get to the issue of school servers we can leverage off the work OLPC has been doing.<br><br>thanks<br>david<br></div></div></div>