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

Support disabling manifest signatures #3537

Open
mharvey-jt opened this issue Mar 14, 2024 · 0 comments
Open

Support disabling manifest signatures #3537

mharvey-jt opened this issue Mar 14, 2024 · 0 comments

Comments

@mharvey-jt
Copy link
Contributor

It would be useful for us to have unsigned manifests.
This would allow us to remove the signing step from the cvmfs_receiver critical path, and also remove the operational need to maintain and rotate certs.

Proposal:

  • Add a configuration option CVMFS_NO_MANIFEST_SIGNATURE_CHECK that will cause manifest validation
    static Failures DoVerify(unsigned char *manifest_data, size_t manifest_size,

    to unconditionally skip signature validation, (avoiding the fetch of .cvmfswhitelist, and the X field object).
  • Add a configuration option CVMFS_NO_SIGN_MANIFEST that will cause publishing pathways to avoid performing any signing of new manifests, producing a manifest with no X field or signature block, and not trying any X object upload.
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

1 participant