#6640 NORM Never A: Input to Rainbow can trigger an assertion failure

[Zarro Boogs per Child]

#6640: Input to Rainbow can trigger an assertion failure
-----------------------+----------------------------------------------------
  Reporter:  bemasc    |       Owner:  mstone        
      Type:  defect    |      Status:  new           
  Priority:  normal    |   Milestone:  Never Assigned
 Component:  security  |     Version:                
Resolution:            |    Keywords:                
  Verified:  0         |    Blocking:                
 Blockedby:            |  
-----------------------+----------------------------------------------------
Changes (by tomeu):

 * cc: tomeu (added)


Comment:

 I'm not sure what's the best solution, but certainly think that the error
 message that appeared in the logs should be much more clear.

 For reference:

 {{{
 /usr/lib/python2.5/site-packages/rainbow/inject.py in check_cwd(uid=10004,
 gid=10031, cwd=dbus.UTF8String('/home/olpc/Activities/Qirat.activity'))
     225     ck = Checker(cwd, uid, gid)
     226     assert ck.positive(R_OK | X_OK, S_IFDIR)
 --> 227     assert ck.negative(W_OK, 0)
         ck.negative = <bound method Checker.negative of
 <rainbow.util.check_access.Checker object at 0xb7530a4c>>
         global W_OK = 2
     228
     229 def check_spool(spool, owner_uid, owner_gid):

 <type 'exceptions.AssertionError'>:
 }}}

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