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

generateForwardingMaterial: proxy all encryption keys #182

Merged
merged 1 commit into from
Aug 9, 2023

Conversation

larabr
Copy link
Contributor

@larabr larabr commented Aug 8, 2023

Also, add doesKeySupportForwarding.

Previously, we only proxied the first encryption subkey. Now, the generated forwardee key will include a subkey for each encryption key of the forwarder key. Multiple proxy parameters will also be returned.

Due to the change, we enforce that all encryption [sub]keys are compatible with forwarding.

@larabr larabr requested review from twiss and wussler August 8, 2023 12:28
…SupportForwarding`

Previously, we only proxied the first encryption subkey.
Now, the generated forwardee key will include a subkey for each encryption key
of the forwarder key. Multiple proxy parameters will also be returned.

Due to the change, we enforce that all encryption [sub]keys are compatible with forwarding.
@larabr larabr force-pushed the forwarding-multiple-subkeys branch from 7b9d103 to 23856c1 Compare August 8, 2023 15:28
@larabr larabr merged commit 5c069ca into ProtonMail:main Aug 9, 2023
1 check passed
larabr added a commit to larabr/pmcrypto that referenced this pull request Feb 20, 2024
…SupportForwarding` (ProtonMail#182)

Previously, we only proxied the first encryption subkey.
Now, the generated forwardee key will include a subkey for each encryption key
of the forwarder key. Multiple proxy parameters will also be returned.

Due to the change, we enforce that all encryption [sub]keys are compatible with forwarding.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants