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

[🚀 | Feature request]: Port: Sequester #6407

Open
2 of 8 tasks
mmmarcos opened this issue Feb 12, 2024 · 1 comment · Fixed by #6644
Open
2 of 8 tasks

[🚀 | Feature request]: Port: Sequester #6407

mmmarcos opened this issue Feb 12, 2024 · 1 comment · Fixed by #6644
Assignees
Labels
C-Feature-Request Category: A feature request for Parsec v3-porting Porting from v2 to v3
Milestone

Comments

@mmmarcos
Copy link
Contributor

mmmarcos commented Feb 12, 2024

Sequester service must be ported to the V3 branch (master).

Brief description

The sequester service allows to recover an organization's entire data set. It can only be activated when the organization is created (the authority key is signed with the organization root secret key).

The typical use case for this service: an investigation is carried out by an inspection service requiring access to data stored on the workspaces of the person(s) involved in the investigation. Note that the secret parts of both authority and service keys are only used in an off-line mode (i.e. no direct communication with the Parsec server is required), so that they can be stored in a secure location and the environment in which they are used can be controlled as much as possible.

V2 Implementation

User documentation is missing (see #2477), but there are some Resana-Secure documents explaining how to use it (ask @Landeers).

V3

Task List:

Related open issues (needs re-triage):

@mmmarcos mmmarcos added C-Feature-Request Category: A feature request for Parsec v3-porting Porting from v2 to v3 labels Feb 12, 2024
@mmmarcos mmmarcos added this to the v3.1 milestone Feb 12, 2024
@mmmarcos mmmarcos removed this from the v3.1 milestone Feb 28, 2024
@mmmarcos mmmarcos added this to the v3.1 milestone May 31, 2024
@mmmarcos mmmarcos removed this from the v3.1 milestone Jun 14, 2024
@mmmarcos mmmarcos mentioned this issue Oct 8, 2024
17 tasks
@mmmarcos mmmarcos added this to the Q4-2024 milestone Oct 11, 2024
@mmmarcos mmmarcos modified the milestones: Q4-2024, v3.4 Nov 5, 2024
@mmmarcos mmmarcos linked a pull request Nov 29, 2024 that will close this issue
4 tasks
@mmmarcos mmmarcos added I-Rust Impact: Rust-related stuff v3-porting Porting from v2 to v3 and removed v3-porting Porting from v2 to v3 I-Rust Impact: Rust-related stuff labels Nov 29, 2024
@mmmarcos mmmarcos modified the milestones: v3.4, v3.3 Dec 9, 2024
@mmmarcos mmmarcos reopened this Jan 16, 2025
@mmmarcos
Copy link
Contributor Author

I've reopened this issue because #6644 does not fully port Sequester feature.

There is still ongoing work (#9342 #9343) and API version is yet to be bumped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-Feature-Request Category: A feature request for Parsec v3-porting Porting from v2 to v3
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants