-
Notifications
You must be signed in to change notification settings - Fork 258
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
CoreCLR restore needs to ignore feeds with encryption #2942
Comments
What we are going to do short term- Change the error message to say: Password decryption is not supported on this platform (windows/dotnetcore). The following feed uses an encrypted password: 'https://msasg.pkgs.visualstudio.com/DefaultCollection/_packaging/PrototypeDotNetCoreSupport/nuget/v3/index.json'. You can use a clear text password as a workaround, or pass it on the commandline |
This issue will only cover the story for the error message. #1851 tracks the full support |
Please use proper brand strings:
|
please keep up until you port this change into b2. |
Please correct the message before merging. Interactive password is not supported on .NET Core. Encrypted passwords are not supported on all platforms not just Windows. |
I'd suggest this message format instead
|
Correct the message and checked into dev and 3.5.0-beta2 |
When a user adds a Nuget feed so they can push to it, VSTS will instruct them to run a command like this:
nuget sources add -name "TestFeedForBug" -source https://thiswouldbemyfeed -username "username" -password "anencryptedpassword"
This adds the feed to the global nuget.config, along with key information in the tag.
When that is present, restoring running on CoreCLR fails. This is exposed through the CLI, which means VS with the .NET Core SDK installed will fail to restore .NET Core projects.
Instead of just failing, on CoreCLR Nuget should ignore feeds which have credentials like this.
Repro:
--packages is important for the repro as if everything can be satisfied by your cache you won't hit the correct codepath.
The config XML below has fake values, but still hits the correct codepath. The top of the stack you should see is also below (you'll first hit a failure because the URL is fake, which can be ignored.)
The text was updated successfully, but these errors were encountered: