8000 Lamport clock can be set far into future making db progress halt · Issue #512 · orbitdb/orbitdb · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Lamport clock can be set far into future making db progress halt #512
Open
@DanielVF

Description

@DanielVF

The main building block of OriginDB is an ordered log, with the ordering being handled at the protocol level.

However the current ordering by a Lamport Clock can trivially be manipulated by a malicious writer to insert entries into almost any specific location desired in the log. This breaks the rough ordering "guarantees" that the Orbit DB protocol provides.

A malicious user could also set the clock to a high value, say Math.pow(2, 54), which when adding one to in Javascript returns the same number. This would break all future entry ordering on a given database, forever.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0