Skip to content
This repository was archived by the owner on Feb 1, 2018. It is now read-only.
This repository was archived by the owner on Feb 1, 2018. It is now read-only.

Support alternative prekeys schedule #70

Description

@hayeah

I am thinking of a use case where prekeys are set to expire at a time schedule (for example, one PreKey everyday), rather than on a take-and-consume basis.

I'd like to design a communication protocol which can obscure the fact that Alice and Bob are talking, and not having a central server to coordinate the prekeys.

Here's my thinking of how such a protocol could work:

  • Bob posts his prekeys publicly, say 365 of them, one per day.
  • Alice grabs the prekey for today, encrypts the message, and posts to a public message hub.
  • Bob listens to the public hub and attempts to decrypt all the messages sent through it.
  • Bob would only be able to decrypt messages encrypted with his prekey for a particular day. These are the messages meant for him.

Surveillance would only be able to see that Alice is sending messages to the hub, but would have no idea who's on the receiving end.

I've looked at the code, and it looks like I need to disable automatic prekey refill and removal. Right now there's no clean way to do it... would it be possible to add hooks to the store to do this?

Maybe something like:

public markPrekeyForRemoval(id: number)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions