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 extra_root_certificates and accept_invalid_certificates when fetching/publishing #127

Open
brooksmtownsend opened this issue Nov 7, 2024 · 3 comments

Comments

@brooksmtownsend
Copy link
Contributor

Often with internal registries there are self-signed certificates in use that are interpreted as invalid. I would love to be able to either specify these flags to ignore invalid certs and supply additional certs to trust at least in the wasm-pkg-client library, and perhaps even with the wkg CLI as well.

If there's appetite for this to be contributed, I'm happy to add this feature

@brooksmtownsend
Copy link
Contributor Author

Also, if there's some way to do this today and I'm just missing it, please let me know!

@lann
Copy link
Collaborator

lann commented Nov 7, 2024

You should be able to set the SSL_CERT_FILE env var (per the rustls-native-certs crate) to point at alternative root(s) but I haven't tried.

@tylerhjones
Copy link

I think you would need to update the registry to include the feature supporting the native tls. It looks like the defaults do not support the use of alt certs; https://github.com/bytecodealliance/registry/blob/main/crates/client/Cargo.toml#L13
So afaik, you need to update the stack all the way down so the features enabled will allow this

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

3 participants