1 / 10

Credential Verification in Mobile Ad-hoc Networks

Credential Verification in Mobile Ad-hoc Networks. Team Challenger 2/21/2005. Overview. Description Design Improvements System Analysis Lessons Learned. Description. No Central Authority, so use your friends! Use a friend to verify your credentials. Friend gives you an assertion.

aquila
Télécharger la présentation

Credential Verification in Mobile Ad-hoc Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Credential Verification in Mobile Ad-hoc Networks Team Challenger 2/21/2005

  2. Overview • Description • Design • Improvements • System Analysis • Lessons Learned

  3. Description • No Central Authority, so use your friends! • Use a friend to verify your credentials. • Friend gives you an assertion. • Use this assertion to prove that what you say is true. • As long as there is a friend in common, you can perform transactions with nodes that are not your friends!

  4. Design • Trust Object (Trust Tester) • Key Ring • Black List • Trust Simulator (Trust Sim) • Spawns Trust Object Threads • Observes threads and dumps data to a “dot” file for viewing with GraphViz software.

  5. Improvements • Certificate timestamps • Policies can be established for certificate validation • Blacklisting • Revoking trust from malicious nodes • Junior trust timeouts • Truly temporary trust

  6. System Analysis • Temporary Trust • No blacklisting • Full blacklisting • Partial blacklisting

  7. Temporary Trust/No Blacklisting • sammy 80 arnold helen • arnold 90 sammy brian charlie • brian 50 arnold • charlie 20 arnold helen • helen 30 sammy charlie

  8. Full Blacklisting Eventually everyone that doesn’t have 100% goodness get blacklisted

  9. Partial Blacklisting Will take longer for a node that has a high goodness to be blacklisted

  10. Lessons Learned • Realistic goals very important • Making deadlines and sticking to them • Bug tracking system, a good development environment, and CVS are all essential tools for programmers • Good communication between team members is necessary for higher productivity • Credential verification in ad-hoc networks

More Related