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

[3.0] [future-work] Cryptographic auth for headers #154

Open
bchess opened this issue Jun 27, 2024 · 0 comments
Open

[3.0] [future-work] Cryptographic auth for headers #154

bchess opened this issue Jun 27, 2024 · 0 comments
Assignees
Labels
schema-change label for 3.0-dev work that involves schema changes
Milestone

Comments

@bchess
Copy link
Contributor

bchess commented Jun 27, 2024

From @Eta0

Add cryptographic authentication / checksums / ECC (if we're getting fancy) for the entire metadata and header section of the file, as a unit, since this allows checking that the metadata is complete and not missing entries (which could potentially happen if, say, the metadata length segment wasn't set properly at serialization time, or ended up changing somehow).

@bchess bchess added this to the 3.0 milestone Jun 27, 2024
@bchess bchess added the schema-change label for 3.0-dev work that involves schema changes label Jun 27, 2024
@Eta0 Eta0 self-assigned this Jul 3, 2024
@Eta0 Eta0 changed the title [3.0] [future-work] Crytographic auth for headers [3.0] [future-work] Cryptographic auth for headers Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
schema-change label for 3.0-dev work that involves schema changes
Projects
None yet
Development

No branches or pull requests

2 participants