-
Notifications
You must be signed in to change notification settings - Fork 26
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
Allow the possibility to skip ca certificates validation #6
Comments
From what I can tell it doesn't work on any non-windows platforms. Could it be related to this problem? Can you just make a flag to turn off validation completely? My suggestion would be to make the HttpClientHandler injectable, but since this whole lib is "static galore", I guess that's not really an option. So just stick a property to the main Tinify class. |
Can you please merge the PR as it would be nice to be able to run Tinify inside a linux docker container. |
What version of Linux are you using? We have used Ubuntu version 18.04 as well as 16.04 running .NET core 3.0, and we are unable to reproduce it. |
Hi ! |
We have no plans to add a flag for skipping CA validation as that is bad practice and should be unnecessary. I got the tinify API client working with the mcr.microsoft.com/dotnet/aspnet:5.0-buster-slim docker image as well. @quentinR0bert Could you share what version of .netcore you are using? |
Hi ! Thanks for the answer, we understand the bad practice about security. The .Net Core CLI project target .Net Core 3.0 and the .Net Library with the Tinify NuGet target .Net Standard 2.1 |
FYI i have just downloaded the source code and executed the test as marked in the readme. The "dotnet test test/Tinify.Tests" is okay. but i have 4 failed test for the Integration tests (by default the sample is on .netCore 2.0, i have the same error in .netCore 3.0 and 3.1) (Some MSBuild part is in french sorry :-/ ) |
Thanks for sharing! I can confirm that the client does not work on mac OS. Currently it works on: Since it seems to be dotnet implementation specific to mac OS or underlying libraries, we are not looking into this right now. I suggest you use Docker for building and running your dotnet app. |
For non windows platforms there are some issues with the certificates validations on nonssl installs. There should be a workaround to skip that validation while Microsoft works on this issue
The text was updated successfully, but these errors were encountered: