Crowdshare, Secure Resource Sharing in Mobile Crowds

Download Crowdshare, Secure Resource Sharing in Mobile Crowds

Post on 18-Dec-2014




0 download

Embed Size (px)




<ul><li> 1. CrowdShareSecure Resource Sharing in Mobile Crowds Stanislaus Stelle CASED / TU Darmstadt 8th of March 2013 on Moosecon Joined work withAlexandra Dmitrienko | Ahmad-Reza Sadeghi | Elena Reshetova | Thomas Schneider | N. Asokan 1 </li> <li> 2. Motivation 2 </li> <li> 3. Motivation Resource Sharing 3 </li> <li> 4. Motivation Resource Sharing Collaborative work 4 </li> <li> 5. Motivation Resource Sharing Collaborative work Social Networks 5 </li> <li> 6. Motivation Resource Sharing Collaborative work Social Networks Mobile 6 </li> <li> 7. Depends on Carrier 7 </li> <li> 8. 4.6 billions without Internet 8 </li> <li> 9. 4.6 billions without Internet Focus on Internet Availability 9 </li> <li> 10. What can wedo about it 10 </li> <li> 11. Existing Technology: Tethering Participant Participant Access Point 11 </li> <li> 12. Existing Technology: Tethering Range Participant Participant Access Point 12 </li> <li> 13. Existing Technology: Tethering Range Password Distribution Password Participant Participant Access Point Password 13 </li> <li> 14. Solution: Multihop Resource Sharing 14 </li> <li> 15. How shouldthis work? 15 </li> <li> 16. Mesh Network Routing: BATMAN 16 </li> <li> 17. What aboutsecurity? 17 </li> <li> 18. Link Security </li> <li> 19. Link Security Access Control </li> <li> 20. AnonymityLink Security Access Control 20 </li> <li> 21. Liability AnonymityLink Security Access Control 21 </li> <li> 22. Implementation for AndroidLink Security SSL/VPNAnonymity Registration with Certs.Liability Signed Resource RequestsAccess Control FoF Service </li> <li> 23. And whataboutliability? 23 </li> <li> 24. Liability InternetWantstotether HasInternetConnection 24 </li> <li> 25. Liability 25 </li> <li> 26. Liability 26 </li> <li> 27. Liability 27 </li> <li> 28. Bound to phone number Liability Destination IP, Protocol, Port, Timestamp 28 </li> <li> 29. Liability 29 </li> <li> 30. Liability 30 </li> <li> 31. Liability 31 </li> <li> 32. Liability 32 </li> <li> 33. Liability 33 </li> <li> 34. Liability 34 </li> <li> 35. And whataboutaccesscontrol? 35 </li> <li> 36. Friend of Friend Service Simple alternative Fancy alternative 36 </li> <li> 37. Simple alternative register 37 </li> <li> 38. Simple alternative sync 38 </li> <li> 39. Simple alternative Transmit Whitelists 39 </li> <li> 40. Fancy alternative 40 </li> <li> 41. Challenges WiFi and 3G at the same time WiFi in Ad-Hoc mode Dynamic Access Control </li> <li> 42. WiFi and 3G at the same time Android prohibits both to be activatedinsmod /system/lib/modules/bcm4329firmware_path=/system/vendor/firmware/fw_bcm4329.bin </li> <li> 43. WiFi in Ad-Hoc mode No System option in Androidiwconfig eth0 channel 11 essid Mesh mode ad-hocifconfig eth0 netmask up </li> <li> 44. Dynamic Access Control Friend of Friend Service Liability Feature </li> <li> 45. Conclusion1) Design of CrowdShare service for secure resource sharing a. Allows arbitrary people to establish mesh and share resources b. Enables users to decide what and with whom to share c. Ensures anonymity, liability, confidentiality, authenticity2) Implementation for Internet sharing on Android devices a. Extends Serval b. Enables internet sharing c. Brings in a security layer d. Addresses a number of technical challenges </li> <li> 46. T ha n k y ouQues ti ons? </li> <li> 47. Stanislaus Stelle </li> </ul>