Skip to content

Use appointment-specific pre-shared ECDH key (?) #40

Description

@adewes

Currently the provider app shares a single public ECDH key with appointments for users to employ when sending encrypted data. To increase secrecy we should ideally make this key appointment-specific. Currently this is not done as it would require robust synchronization of appointment ECDH keys between different provider apps.

In general we should think about how we can improve the key agreement protocol using e.g. a double or triple Diffie Hellman key agreement schemes following e.g. the Signal protocol.

** Check back with cryptography experts**.

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

    cryptoCryptography-related tasksdiscussIssue for discussion, do not implement yet!

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions