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

Access Intermediate with http/insecureAddress #2145

Closed
rphlwnk opened this issue Jan 21, 2025 · 1 comment
Closed

Access Intermediate with http/insecureAddress #2145

rphlwnk opened this issue Jan 21, 2025 · 1 comment
Assignees

Comments

@rphlwnk
Copy link

rphlwnk commented Jan 21, 2025

Is there a way to access the intermediates.pem or roots.pem through the insecureAddress?

I only get the files when accessing it through https, when I try accessing it through the insecureAddress i get an 404.

My ca.json looks like that

"address": ":4443",
"insecureAddress": ":8080",
"dnsNames": [
                "127.0.0.1",
        ],

When i try accessing it directly on the Server

curl http://127.0.0.1:8080/intermediates.pem
404 page not found

curl https://127.0.0.1:4443/intermediates.pem
-----BEGIN CERTIFICATE-----
MIIG+TCCBeGgA.....
@hslatman
Copy link
Member

hslatman commented Jan 21, 2025

Hi @rphlwnk, at the moment we don't serve the intermediate or root through HTTPS. The reason for this is that to be able to trust the response, we rely on TLS. We currently don't have another way to ascertain that a set of intermediates retrieved via HTTP is the expected set of certificates.

It is unlikely that we'll add support for it, because we'd rather have people bootstrap trust with the CA, and then use HTTPS wherever possible.

@hslatman hslatman self-assigned this Jan 21, 2025
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