You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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**.
The text was updated successfully, but these errors were encountered:
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**.
The text was updated successfully, but these errors were encountered: