secure multicast interest in chronosync
play

Secure Multicast Interest in ChronoSync Yingdi UCLA 1 ChronoSync - PowerPoint PPT Presentation

Secure Multicast Interest in ChronoSync Yingdi UCLA 1 ChronoSync State of a data set Digest State tree modification 00a12... <update /ucla/alice to SeqNo 4 > is expressed as a 3da49a <update /arizona/bob to SeqNo 2 >


  1. Secure Multicast Interest in ChronoSync Yingdi UCLA 1

  2. ChronoSync • State of a data set Digest State tree modification 00a12... <update /ucla/alice to SeqNo 4 > is expressed as a 3da49a <update /arizona/bob to SeqNo 2 > digest 8f904d <update /arizona/bob to SeqNo 1 > c3412e <update /ucla/alice to SeqNo 3 > State Digest dd79f2 <update /ucla/alice to SeqNo 1 > • Maintain a digest Alice's Digest Bob's Digest Cathy's Digest log to identify the Name Prefix Name Prefix Name Prefix state difference Max Seq-No Max Seq-No Max Seq-No 2

  3. Sync interest multicast My current state digest is 4de318f... 3

  4. Identity state digest What is 4de318f ? What is 4de318f ? What is 4de318f ? 4

  5. Recover unknown digest Unknown digest 4de318f Start reconcile 5

  6. If anyone can send multicast interest… 6

  7. To launch attack • Attacker needs to – get prefix of the sync group – generate a large number of sync interests with random digest • All legitimate users will be forced to – do extra lookup – do unnecessary reconciliation – do extra signing • No way to distinguish legitimate sync interests from malicious sync interests 7

  8. Authenticate sync interest • Signed interest • Should not prevent interests from being merged in the network 8

  9. Interest merging Current state is 4de318f... Current state Current state is 4de318f... is 4de318f... Interests representing the same state should be merged 9

  10. Data multicast New updates 10

  11. Authenticate sync interest • Signed interest • Should not prevent interests from being merged in the network – asymmetric signatures do not work • Symmetric signatures – how to distribute the symmetric key? 11

  12. Symmetric Key Distribution • Periodically generate a symmetric key • Encrypt the symmetric key using the each user’s public key • Published as a single packet • Who can generate the symmetric key? – designated user • single pointer failure – any user Name: /ucla/bob/<sync_group>/SyncKey/SeqNo Content: • resolve conflict when Key encrypted using /ucla/alice's public key more than one user Key encrypted using /arizona/bob's public key generate keys at the same time Key encrypted using /memphis/cathy's public key Bob's Signature 12

Recommend


More recommend