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

migrate to supplying x.509 CA certificates in a bundle rather than separate root and intermediate certs #140

Open
ChaosInTheCRD opened this issue Jan 29, 2024 · 2 comments

Comments

@ChaosInTheCRD
Copy link
Collaborator

Currently Witness requires that root certs are supplied separately to intermediate certs like so:

  "roots": {
    "test": {
      "certificate": <base64-encoded-root-cert-pem>,
      "intermediates": [
        <base64-encoded-intermediate-cert-pem>
      ]
    }
  },

Instead, allowing the user to supply all the necessary certs (root and intermediate) as a single pem encoded trustbundle would be an easier experience:

  "roots": {
    "test": {
      "trustBundle": <base64-encoded-trust-bundle-pem>
    }
  },
@ChaosInTheCRD
Copy link
Collaborator Author

it's worth noting that investigating how the upstream in-toto policy language handles this process.

@colek42
Copy link
Member

colek42 commented Jan 31, 2024

I've seen this pattern more in the wild than what we use. If we change it we should try to support the legacy fields.

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