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

Split CAs instead of using a single self-signed root CA #328

Open
Santti4go opened this issue Dec 18, 2024 · 0 comments
Open

Split CAs instead of using a single self-signed root CA #328

Santti4go opened this issue Dec 18, 2024 · 0 comments

Comments

@Santti4go
Copy link

Feature description

Currently the create_keystore command creates a self-signed root Certificate Authority (CA) and uses it for both Permissions CA and Identity CA through symlink.

This approach creates a limitation in how certificates can be managed. Since basically all three CAs (root, Permissions and Identity) are effectively the same, tasks like updating the permissions.xml policy for a single enclave require access to the root CA's private key, which is not ideal. Similarly, adding a cert.pem for a new enclave also requires the root CA's private key. This setup prevents the delegation of responsibilities between the Permissions and Identity CAs.

I've created a PR with these changes. I targeted the Humble branch as it is the one I'm currently using.
Please feel free to dismiss this issue if this functionality is not desired.

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