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

Reserving space in the signature header #183

Closed
n3npq opened this issue Mar 27, 2017 · 1 comment
Closed

Reserving space in the signature header #183

n3npq opened this issue Mar 27, 2017 · 1 comment

Comments

@n3npq
Copy link
Contributor

n3npq commented Mar 27, 2017

The signature header contains (optional) information to verify package integrity.

So new tags are added when packages are signed, and a new signature header is created and inserted into a *.rpm package file.

However, the insertion forces a rewrite of the metadata header and payload, which for a distribution signing event, can rewrite a terabyte of information.

Another flaw with a variable sized signature header is that the metadata header and payload are not located at a constant offset, preventing, say, HTTP byte ranges from directly reading the header metadata blob.

One simple solution is to add a "free space" tag to the signature header to reserve space for a signature (or other data) to be added later. This would permit the new signature header to be rewritten in-place with an adjusted "free space" tag instead of rewriting entire packages when signing.

I will have a patch to add a "free space" tag to a signature header for rpm.org soon.

@pmatilai
Copy link
Member

We've had that for almost three years now so don't bother.

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