-
Notifications
You must be signed in to change notification settings - Fork 705
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
dotnet restore --interactive fails with SSL errors on WSL #97
Comments
Sorry... scratch that part about the plugins dir |
Apparently, this is a dotnet core bug |
Hey @teqdruid , Thanks for filing this issue and finding the root cause! As you said, this is a .NET core bug. Please update your .Net core sdk with the recent versions and let me know if that fixes it. |
Closing this issue. Please let me know if you see this with fixed versions of dotnet core and I'll re-open. Thanks! |
@teqdruid you are using 2.2.300, which is the latest version, it should contain the fix already, right? |
Sorry to take so long, but yes... I was using 2.2.300, which is the latest. (I had implemented the workaround which removed this issue as a blocker.) I think that CredentialProvider.Microsoft needs to upgrade its SDK to resolve this issue on WSL (and presumably Linux). |
Hi Guys-
I'm running WSL (Pengwin) on Win10. I've installed the credprovider. (Though the plugin dir ended up being ~/.nuget/NuGet/plugins). When I run
dotnet restore --interactive
, I get:I'm not sure where to go from here. Is the credprovider not compatible with WSL or am I missing a package...? Is this even a credprovider issue or should I submit this to the .net core team?
The text was updated successfully, but these errors were encountered: