#6943 NORM Opportu: Ghost XO in the presence service

[Zarro Boogs per Child]

#6943: Ghost XO in the presence service
--------------------------------+-------------------------------------------
   Reporter:  yani              |       Owner:  Collabora      
       Type:  defect            |      Status:  new            
   Priority:  normal            |   Milestone:  Opportunity    
  Component:  presence-service  |     Version:                 
 Resolution:                    |    Keywords:  8.2.0:- 9.1.0:?
Next_action:  design            |    Verified:  0              
  Blockedby:                    |    Blocking:                 
--------------------------------+-------------------------------------------
Changes (by mstone):

  * keywords:  8.2.0:? => 8.2.0:- 9.1.0:?
  * priority:  high => normal
  * next_action:  diagnose => design
  * milestone:  8.2.0 (was Update.2) => Opportunity


Comment:

 There are a couple of problems here.

 First, avahi & friends are capable of receiving information insufficient
 to constitute a valid contact with an OLPC Buddy. Yani managed to find an
 XO transmitting such invalid data.

 Second, the current presence service assumes that the relation between
 contacts and keys will, at every moment of time, be one-to-one. This is a
 faulty assumption because there are many ways situations in which two XOs
 could come to share the same key -- intentional pseudonymity, malicious
 disclosure and use of the key, simple accidents with save-nand/copy-nand,
 or the representation of multiple routes to the same XO as multiple
 contacts with that XO.

 It's probably not urgent to revise this design decision but it seems hard
 to fix this bug without doing so. Fortunately, the bug does not seem
 urgent at present.

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