[Trac #260] Implement keyboard and event security in X using XACE

Zarro Boogs per Child bugtracker at laptop.org
Tue Jan 23 06:35:41 EST 2007


#260: Implement keyboard and event security in X using XACE
-----------------------------+----------------------------------------------
 Reporter:  krstic           |        Owner:  ajax 
     Type:  task             |       Status:  new  
 Priority:  high             |    Milestone:  CTest
Component:  x window system  |   Resolution:       
 Keywords:                   |  
-----------------------------+----------------------------------------------
Changes (by jg):

  * priority:  blocker => high

Comment:

 Blocker means "we really can't ship".

 It isn't clear this qualifies as a blocker under any circumstances.

 Its priority, along with any kernel support for isolation, ranks behind
 power management and suspend/resume in our base system work.

 We have to keep our eyes on the prize: a low power laptop trumps just
 about everything, as otherwise the laptop can't be used in many areas of
 the world.  The importance of security increases only as we are into
 serious deployment and start becoming a target.  First things, first....

-- 
Ticket URL: <http://dev.laptop.org/ticket/260#comment:8>
One Laptop Per Child <http://laptop.org/>



More information about the Bugs mailing list