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

Support lack of key generated on getrecipientsharedkey and receiver #24

Open
realvarx opened this issue Jun 16, 2023 · 0 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@realvarx
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

If the shared_key which has to be generated by the other atSign hasn't been generated by the moment that getrecipientsharedkey is called, it won't be possible to decrypt the messages as that situation isn't handled. That leaves the user with no other option that stopping and running again the client.

Describe the solution you'd like

Create a global variable with allows the control of this situation. If the recipientsharedkey wasn't obtained at the first call, the client will try to obtain it when the first message from the recipient atSign is read.

Describe alternatives you've considered

No response

Additional context

No response

@realvarx realvarx added the enhancement New feature or request label Jun 16, 2023
@realvarx realvarx self-assigned this Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant