#8434 NORM Not Tri: ttyUSB devices should be accessible by user olpc

[Zarro Boogs per Child]

#8434: ttyUSB devices should be accessible by user olpc
------------------------+---------------------------------------------------
   Reporter:  pgf       |       Owner:  cscott                           
       Type:  defect    |      Status:  new                              
   Priority:  normal    |   Milestone:  Not Triaged                      
  Component:  security  |     Version:  Development build as of this date
 Resolution:            |    Keywords:                                   
Next_action:  code      |    Verified:  0                                
  Blockedby:            |    Blocking:                                   
------------------------+---------------------------------------------------
Changes (by cscott):

 * cc: mstone (added)
  * owner:  => cscott
  * next_action:  never set => code
  * component:  not assigned => security
  * version:  not specified => Development build as of this date


Comment:

 Copying from the devel thread
 (http://lists.laptop.org/pipermail/devel/2008-September/019135.html):
 {{{
 The XO currently sets the group for /dev/ttyUSB0 to 'uucp'.
 So, my proposal is that (a) the 'olpc' user be added to the 'uucp'
 group, and (b) that the permissions.info file may be used to request
 that the activity's "isolated" UID also be a member of the uucp group.
  (See
 http://wiki.laptop.org/go/Activity_bundles#activity.2Fpermissions.info
 for Michael's documentation of the permissions.info file).

 Does this seem right to you, Michael?  I think rainbow already has a
 mechanism to create local copies of /dev/video etc for access to the
 camera, etc; perhaps he'd prefer to use that mechanism instead.  (I
 personally like trying to use the traditional groups for their
 intended purposes whenever possible, to avoid surprises.)
 }}}

-- 
Ticket URL: <http://dev.laptop.org/ticket/8434#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system