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

Better explain the formatting and length of shared keys #41

Open
cpswan opened this issue Feb 20, 2023 · 2 comments
Open

Better explain the formatting and length of shared keys #41

cpswan opened this issue Feb 20, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@cpswan
Copy link
Member

cpswan commented Feb 20, 2023

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

When we create an AES shared key it will be 256 bits long (== 32 bytes), but the shared key that we find in an atSign is much longer, as it's encrypted with RSA2048, which pushes its size up to 2048 bits (== 256 bytes) before it is then base64 encoded, which takes the total size to around 350 characters

Describe the solution you'd like

Add to the documentation in this repo so that expectations around keys are made clear.

@cpswan cpswan added the enhancement New feature or request label Feb 20, 2023
@cpswan cpswan assigned gkc and cpswan Feb 20, 2023
@gkc
Copy link
Contributor

gkc commented Apr 3, 2023

See also #46

I've covered this in a larger update to the protocol spec for which I will be raising a PR this week. Keeping in sprint but reducing SP to 0

@gkc
Copy link
Contributor

gkc commented May 16, 2023

This didn't get attention during last two sprints; will prioritize closing this out this week

@gkc gkc unassigned cpswan Mar 18, 2024
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

2 participants