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

Create KEYS_BUNDLE_ACCESS for sequester services #6645

Closed
Tracked by #6407
mmmarcos opened this issue Mar 8, 2024 · 0 comments · Fixed by #6644
Closed
Tracked by #6407

Create KEYS_BUNDLE_ACCESS for sequester services #6645

mmmarcos opened this issue Mar 8, 2024 · 0 comments · Fixed by #6644
Labels
A-Server Area: Parsec Server
Milestone

Comments

@mmmarcos
Copy link
Contributor

mmmarcos commented Mar 8, 2024

In Parsec V3 we no longer need to use keys in the file manifest for each block, since we can use the workspace encryption key, EXCEPT for sequester service (since the workspace encryption key is not shared with sequester services, but instead manifests are re-encrypted with keys supplied by these services).

A simple solution would be to stop storing a key in the file manifest for each block, but that's a shame compared to the possibility of just creating a KEYS_BUNDLE_ACCESS for each sequester service (with this, users don't have to upload the metadata several times, so the implementation is just simpler that way \o/)

@mmmarcos mmmarcos added this to the v3.1 milestone Mar 8, 2024
@mmmarcos mmmarcos added the A-Server Area: Parsec Server label Mar 8, 2024
@mmmarcos mmmarcos linked a pull request Mar 8, 2024 that will close this issue
4 tasks
@mmmarcos mmmarcos modified the milestones: v3.0, v3-next Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Server Area: Parsec Server
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant