-
-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Ignore self-signed certificate option #84
Comments
I'm not sure this is related to Himalaya. A self-signed cert can be trusted from the OS side, like in this post: sudo trust anchor --store self-signed.crt |
I don't know how to use |
We could attach a new property to the config but it requires some work. This is clearly not a priority for the |
My use case is mainly for testing with greenmail which generates a new cert at each run. |
With great pleasure 😉 feel free to use the discussion feature if needed! |
Enabling self-signed certificates (and/or non-encrypted connections) would allow to play with test servers like GreenMail (and write some CI functional tests ?).
The text was updated successfully, but these errors were encountered: