You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rob adding text on 2/10/2017:
nuget.exe | dotnet.exe can now use encrypted passwords in nuget.config files -- when running on windows ONLY.
Ideally, we'd support dotnet.exe on other platforms too, so they don't need to store passwords via cleartext.
Reacted by Nils Hjelte, Swoorup Joshi, Alexander Trauzzi, Niharika Dutta, Wei Zheng, Heinrich Ulbricht, Peter Smulovics, Brian McBrayer, Bill Boggs, Charles Villard and 31 more
I know it's not related directly. As I said (I think), I'm using a client-cert certificate that runs over https, I'm currently having to use the http version (which doesn't have client-cert or encryption) though because I don't want to store the client-cert certificate password unencrypted. I could probably set up a https proxy that doesn't require client-cert as well, but I don't want to accidentally expose it outside of the machine so I have intentionally used the http one on localhost instead of doing that. Ideally I'd like this feature to be implemented so I don't have to use the http one or find a different solution at all.
:
I just started getting this warning:
<path to .csproj> : warning NU1803: You are running the 'restore' operation with an 'HTTP' source, 'http://<rest of link>'. Non-HTTPS access will be removed in a future version. Consider migrating to an 'HTTPS' source.
I'm currently using http on macOS (on localhost, which probably should
never be blocked imo since it's not really insecure in the same way per-se)
because it doesn't support encrypting the client-cert certificate for some
reason. This should be able to be very secure on macOS using keychain, I
have no idea why this isn't supported yet other than low priority (which is
understandable), but I need to be able to keep using http for localhost
until client-cert is implemented on macOS - will disallowing http be
delayed until this is implemented on all platforms?
Is there a timeline for this? Will it be properly secure using keychain
(if I'm not mistaken keychain will prompt every time access is requested
until allow every time is pressed, and then it should allow for the dotnet
executable to access its keychain data)?
—
Reply to this email directly, view it on GitHub
<#1851 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAH2LEEGBTNPX5N2XNVD3Q3VVR57LANCNFSM4BW7LB2Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Still a problem today. OS's have built-in key chain managers so I wonder why it's not compatible?
We can't be moving developers over to Linux / Mac if we MSFT is forcing them to store plain text.
I understand that ProtectedData is too tightly coupled with Windows's DPAPI, but .NET also has ISecureStorage via Microsoft.Maui.Storage. It seems that's already a drop-in replacement
for Windows, where it uses DataProtectionProvider, i.e. presumably the same DPAPI
for macOS (and iOS / iPadOS, which may not be useful for this issue), where it uses Keychain
for Android, which probably isn't that useful here
For Linux, it seems org.freedesktop.secrets is a good starting point that GNOME Keyring and KDE Wallet (and presumably others?) seem to adopt.
Given that, how about
making NuGet Client depend on Microsoft.Maui.Essentials instead of ProtectedData (which would already solve this ticket for developers on macOS)
expanding MAUI Essentials to support org.freedesktop.secrets
I understand that ProtectedData is too tightly coupled with Windows's DPAPI, but .NET also has ISecureStorage via Microsoft.Maui.Storage. It seems that's already a drop-in replacement
* for Windows, where it uses `DataProtectionProvider`, i.e. presumably the same DPAPI
* for macOS (and iOS / iPadOS, which may not be useful for this issue), where it uses `Keychain`
* for Android, which probably isn't that useful here
For Linux, it seems org.freedesktop.secrets is a good starting point that GNOME Keyring and KDE Wallet (and presumably others?) seem to adopt.
Given that, how about
1. making NuGet Client depend on `Microsoft.Maui.Essentials` instead of `ProtectedData` (which would already solve this ticket for developers on macOS)
2. expanding MAUI Essentials to support org.freedesktop.secrets
I’m not an expert in this area, so I may be missing something, but would NuGet Client actually need to depend on Microsoft.Maui.Essentials?
Since org.freedesktop.secrets is a standard D-Bus API, it should be possible to access it directly from C# using a D-Bus client or existing .NET bindings. MAUI’s ISecureStorage could provide a useful abstraction, but it does not seem strictly necessary for implementing Linux support.
I'm flabbergasted this was closed as not planned after 10 years.
Quoting Sean Iyer (@seaniyer), Sr Product Manager with the NuGet team in the What's New in NuGet video, published on November 13, 2025.
In this session, we would like to show how those tools are getting smarter, powered by AI, and how the ecosystem is becoming more trustworthy thanks to the new security features.
He talks about NuGet MCP Server (AI), then trusted publishing and NuGet audit (security).
But shouldn't security start with the basics, like not having a clear text password for private NuGet feeds in the ~/.nuget/NuGet/NuGet.Config file‽
Activity
yishaigalatzer commentedon Dec 18, 2015
CC @anurse @davidfowl
emgarten commentedon Feb 4, 2016
Is this needed for xplat?
yishaigalatzer commentedon Feb 4, 2016
Yes but not for rc, and debatable for rtm
73 remaining items
zivkan commentedon Jul 25, 2022
@hamarb123 this issue (source password encryption, for private/authenticated feeds) is not related to http/https. Please create a new issue for that.
hamarb123 commentedon Jul 26, 2022
I know it's not related directly. As I said (I think), I'm using a client-cert certificate that runs over https, I'm currently having to use the http version (which doesn't have client-cert or encryption) though because I don't want to store the client-cert certificate password unencrypted. I could probably set up a https proxy that doesn't require client-cert as well, but I don't want to accidentally expose it outside of the machine so I have intentionally used the http one on localhost instead of doing that. Ideally I'd like this feature to be implemented so I don't have to use the http one or find a different solution at all.
tmds commentedon Oct 11, 2022
p10tyr commentedon Dec 6, 2024
Still a problem today. OS's have built-in key chain managers so I wonder why it's not compatible?
We can't be moving developers over to Linux / Mac if we MSFT is forcing them to store plain text.
p10tyr commentedon Dec 6, 2024
https://learn.microsoft.com/en-us/nuget/consume-packages/consuming-packages-authenticated-feeds
Entroper commentedon Oct 7, 2025
Coming up on 10 years for this one. Any updates?
hicham-bouchikhi commentedon Jul 28, 2026
Still nothing boys
chucker commentedon Jul 29, 2026
I understand that
ProtectedDatais too tightly coupled with Windows's DPAPI, but .NET also hasISecureStorageviaMicrosoft.Maui.Storage. It seems that's already a drop-in replacementDataProtectionProvider, i.e. presumably the same DPAPIKeychainFor Linux, it seems org.freedesktop.secrets is a good starting point that GNOME Keyring and KDE Wallet (and presumably others?) seem to adopt.
Given that, how about
Microsoft.Maui.Essentialsinstead ofProtectedData(which would already solve this ticket for developers on macOS)hicham-bouchikhi commentedon Aug 3, 2026
I’m not an expert in this area, so I may be missing something, but would NuGet Client actually need to depend on Microsoft.Maui.Essentials?
Since
org.freedesktop.secretsis a standard D-Bus API, it should be possible to access it directly from C# using a D-Bus client or existing .NET bindings. MAUI’sISecureStoragecould provide a useful abstraction, but it does not seem strictly necessary for implementing Linux support.jebriede commentedon Aug 10, 2026
Today, the best way to accomplish this is to use the credential provider. For example, Azure Artifacts supports the credential provider: https://github.com/microsoft/artifacts-credprovider. There are no immediate plans to support encrypted secrets in the NuGet.config. Other ways to provide secrets to NuGet include the NUGET_API_KEY environment variable (see https://learn.microsoft.com/en-us/nuget/reference/cli-reference/cli-ref-environment-variables) for push and for restore NuGetPackageSourceCredentials_{name} (see https://learn.microsoft.com/en-us/nuget/consume-packages/consuming-packages-authenticated-feeds#credentials-in-nugetconfig-files).
0xced commentedon Aug 30, 2026
I'm flabbergasted this was closed as not planned after 10 years.
Quoting Sean Iyer (@seaniyer), Sr Product Manager with the NuGet team in the What's New in NuGet video, published on November 13, 2025.
He talks about NuGet MCP Server (AI), then trusted publishing and NuGet audit (security).
But shouldn't security start with the basics, like not having a clear text password for private NuGet feeds in the
~/.nuget/NuGet/NuGet.Configfile‽