-
Notifications
You must be signed in to change notification settings - Fork 38
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: Shamir-based shared recovery device #6090
Labels
Milestone
Comments
mmmarcos
added
C-Feature-Request
Category: A feature request for Parsec
v3-porting
Porting from v2 to v3
labels
Jan 9, 2024
mmmarcos
changed the title
[V3] Port: Shamir-based shared recovery device
[🚀 | Feature request]: Port: Shamir-based shared recovery device
Jan 9, 2024
This was referenced May 16, 2024
With @vxgmichel we discussed the possibility of adding a few checks that are technically valid but make the shamir questionable:
|
This was referenced Oct 30, 2024
@vxgmichel I've added a Test protocol section to the issue description. Please complete so we can use it to test the feature when its finished. |
2 tasks
Before closing, we should add the corresponding newsfragment (see #9232 (comment)) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Shamir-based shared recovery device is described in RFC 1000.
It was implemented for the V2 branch in the following PRs:
It must be ported to the V3 branch (
master
).NOTE: V2 implementation was CLI-based, so the GUI part (#8671) is out of scope for the moment.
Task List
[Shamir port] server side list_shared_recovery_devices #7360(edit: it's already in get_certificates)Client::shamir_setup_create
#8206sharks
withblahaj
? #8990The GUI would not be implemented right now, so we can leave the following issue for later:
Test protocol
Setup
TODO: Describe how to local setup for testing this feature (testbed ? local server ? ...)
Tests
TODO: List some test cases to be performed when reviewing the feature.
The text was updated successfully, but these errors were encountered: