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

[standards] Securing mechanisms section could be structured better #17

Open
Sakurann opened this issue Aug 8, 2024 · 1 comment
Open
Assignees

Comments

@Sakurann
Copy link

Sakurann commented Aug 8, 2024

this is not urgent, but Securing Mechanisms section could be organized clearer I think. some thoughts:

  • I think sd-bls uses data integrity, so should be moved to embedded
  • would really encourage to separate crypto (BBS) from the format as much as possible (might not be always possible)
  • enveloped section should probably be bulleted into JWT and SD-JWT, COSE (not sure what is a better name for mdoc), SD-CWT
@simoneonofri simoneonofri self-assigned this Aug 8, 2024
@simoneonofri
Copy link
Contributor

Hi @Sakurann,

Thank you for the comment:

  • I re-read the paper and talked with the authors. In theory, it can be both, but the actual status is more of a signature algorithm. I'm going to move it.
  • I agree that it is not an optimal organization, but it is coherent with VCDM/OIDF/OWF terminology. In theory, it should be good to have formats with crypto agility and to apply crypto algorithms (also in the Threat Model they are a different thing)
  • Formatting, a nice idea, maybe also a table.

@simoneonofri simoneonofri changed the title Securing mechanisms section could be structured better [standards] Securing mechanisms section could be structured better Aug 14, 2024
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

No branches or pull requests

2 participants