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.

Sign up for GitHub

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

Jump to bottom

Refactor the distributed schemes for the new API #19

Open
rheitjoh opened this issue Apr 7, 2021 · 1 comment
Open

Refactor the distributed schemes for the new API #19

rheitjoh opened this issue Apr 7, 2021 · 1 comment
Labels
Gitlab Old issue moved over from Gitlab repository

Comments

@rheitjoh
Copy link
Member

rheitjoh commented Apr 7, 2021

(This issue has been imported from the Gitlab repository because it seems to not have been addressed yet)

Original Text (Issue 52)

This should be done after the keys (public parameters, public key, private keys) are representable. More specific, they should be decoupled and implemented as separated classes. Then they should know how to represent themselves.

Comments

Refer to the original issue for comments.
@rheitjoh rheitjoh added the Gitlab Old issue moved over from Gitlab repository label Apr 7, 2021
@rheitjoh rheitjoh changed the title [CrACo] Refactor the distributed schemes for the new API Refactor the distributed schemes for the new API Apr 7, 2021
@rheitjoh
Copy link
Member Author

rheitjoh commented Apr 7, 2021

Seems like there was work on this issue on branch https://git.cs.upb.de/ag-bloemer/sis/compare/develop...52-craco-refactor-the-distributed-schemes-for-the-new-api .

Also potentially related to #15 as that branch also contains that scheme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Gitlab Old issue moved over from Gitlab repository
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rheitjoh