Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • drasyl drasyl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SANE (Public)SANE (Public)
  • drasyldrasyl
  • Issues
  • #62
Closed
Open
Issue created Jun 11, 2020 by bornholdt@bornholdtOwner

Super Peer should provide proof that specified client has joined him

Currently, any super peer can announce that a certain other node has joined him as a client. A harmful super peer could thus intentionally spread false routing information to other super peers. To prevent this, the super peer should provide proof, which shows that the client has joined him as a client.

Since a client can change its super peer over time, multiple valid proofs can exist that client. To allow the system to identify the current super peer, proofs must be chronologically sortable.

Edited Feb 02, 2022 by bornholdt
Assignee
Assign to
Time tracking