Ticket #1502 (new task)

Opened 7 years ago

Last modified 6 years ago

Security control panel

Reported by: jg Owned by: Eben
Priority: normal Milestone: Future Release
Component: security Version:
Keywords: security Cc: krstic, holger, mstone, eben, cscott
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking: #6428

Description

The activity security system needs a GUI designed for its control.

Change History

  Changed 7 years ago by Eben

  • status changed from new to assigned

Ivan, could I get a functional spec (or link thereto) for the security system?

  Changed 7 years ago by kimquirk

  • verified unset
  • milestone changed from BTest-4 to Trial-2

Moved to next SW release, Trial-2.

  Changed 7 years ago by holger

  • cc holger added

  Changed 7 years ago by jg

  • milestone changed from Trial-2 to Trial-3

  Changed 7 years ago by mstone

  • cc mstone added

  Changed 7 years ago by krstic

  • owner changed from Eben to krstic
  • priority changed from high to normal
  • status changed from assigned to new
  • component changed from distro to security
  • milestone changed from Trial-3 to V1.1

A CLI will be present for FRS. A proper GUI is post-FRS material. I'll take back ownership to produce a functional spec for it.

  Changed 7 years ago by Eben

This might be covered by #3239, unless we want to force a reboot with modifier to access it.

follow-up: ↓ 9   Changed 7 years ago by sj

  • priority changed from normal to high

If users are going to be prevented from installing the activities of their choice until they can figure out how this works, making this simple to use and/or well-documented is necessary, not just another feature. Making this part of the solution to #3239 sounds reasonable.

in reply to: ↑ 8   Changed 7 years ago by krstic

  • priority changed from high to normal

Replying to sj:

If users are going to be prevented from installing the activities of their choice until they can figure out how this works

They're not. Please don't change bug priorities without consulting with bug owner or Jim/Kim.

  Changed 6 years ago by cscott

  • owner changed from krstic to cscott
  • next_action set to never set

I'll take this one. I'm a sugar-control-panel wizard now!

  Changed 6 years ago by cscott

  • cc eben, cscott added
  • owner changed from cscott to Eben
  • summary changed from Security system will need a GUI designed. to Security control panel

From discussion with Eben: there are three sections to this control panel:

  • Theft-deterrence
    • Last check in with theft-deterrence server
    • Time current lease expires
    • Manual lease renewal button
    • "Where in the world am I" button (poorly defined, but this is information from the theft-deterrence server: maybe school name, maybe location based on IP address, maybe something else?)
    • Black list check button (check right now w/ the update server and let me know right away if this machine is stolen, not stolen, or "can't tell"). When someone is trying to sell you an XO, have them take you to the nearest internet cafe and click this button before you hand over your money.
  • Developer key
    • Status: installed, temporarily disabled, requested but not yet issued, or not present.
    • Request/fetch developer key button.
  • Bitfrost (http://wiki.laptop.org/go/OLPC_Bitfrost)
    • "Almost all of the protections we discuss can be disabled by the user through a graphical interface"
    • For 9.1: P_SF_CORE / P_SF_RUN

Reassigning to Eben for GUI mockups. Reassign back to me when ready to implement.

  Changed 6 years ago by cscott

  • blocking 6428 added

(In #6428) This bug has been absorbed by #1502.

  Changed 6 years ago by bert

IMHO a user doesn't even have to know there is a "dev key". So why not simply have a checkbox labeled something like "allow running test builds"? I'm not even sure it has to live in the security panel ... KISS rules ;)

Note: See TracTickets for help on using tickets.