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

Feature Request: Option to disable strict SSL #2283

Closed
PaulHMason opened this issue Dec 19, 2019 · 4 comments
Closed

Feature Request: Option to disable strict SSL #2283

PaulHMason opened this issue Dec 19, 2019 · 4 comments

Comments

@PaulHMason
Copy link

I'm behind a corporate firewall the uses a self-signed certificate for SSL interception which breaks pub for Dart and Flutter. I haven't been able to get any of the proposed solutions to work (proxy and certificate path). Other package managers (npm and bower) offer the option to disable strict SSL - would it not be possible to do this with pub as well?

@kiran-cmyk
Copy link

Hi Paul, Did you find any workaround to resolve this issue?

@PaulHMason
Copy link
Author

Hi Paul, Did you find any workaround to resolve this issue?

Unfortunately not - I've tried all the things with certificate paths that I've found, but nothing works. It pretty much puts Flutter out of the running for me.

@jonasfj
Copy link
Member

jonasfj commented May 11, 2020

Have you tried setting the environment variable: DART_VM_OPTIONS="--root-certs-file=path/to/cert.pem" (disclaimer I haven't tried to reproduce the issue)

Also set environment variables: https_proxy, http_proxy (see Troubleshooting pub).

Before doing pub run, flutter pub get or flutter packages get. Check that the certificate PEM encoded?

What OS are you on?


I think adding a --ca-file=path/to/file.pem flag to pub would be more reasonable (I think that's what motivated flutter/flutter#56607).
Allowing users to disable TLS outright seems dangerous... From what I can see npm currently advocates a config option to set a custom certificate.

@sigurdm
Copy link
Contributor

sigurdm commented Feb 13, 2023

Closing as stale as there was no response.

Please open a new issue if this is still a problem, and the suggestion above didn't help.

@sigurdm sigurdm closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2023
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

4 participants