Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
adewes opened this issue Dec 3, 2021 · 0 comments
Open

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

adewes opened this issue Dec 3, 2021 · 0 comments
Labels
crypto Cryptography-related tasks discuss Issue for discussion, do not implement yet!

Comments

@adewes
Copy link
Member

adewes commented Dec 3, 2021

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**.

@adewes adewes added the crypto Cryptography-related tasks label Dec 3, 2021
@adewes adewes changed the title Use appointment-specific pre-shared ECDH keys Use appointment-specific pre-shared ECDH keys (?) Dec 3, 2021
@adewes adewes added the discuss Issue for discussion, do not implement yet! label Dec 3, 2021
@adewes adewes changed the title Use appointment-specific pre-shared ECDH keys (?) Use appointment-specific pre-shared ECDH key (?) Dec 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crypto Cryptography-related tasks discuss Issue for discussion, do not implement yet!
Projects
None yet
Development

No branches or pull requests

1 participant