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
With Chocolatey CLI v2.2.2 (well all v2.x versions I think), when pushing to a http source, a warning from the NuGet assemblies is shown: [NuGet] You are running the 'push' operation with an 'HTTP' source, 'http://nexus.repo/repository/choco/'. Non-HTTPS access will be removed in a future version. Consider migrating to an 'HTTPS' source.
This warning can be read as Chocolatey moving to having https everywhere as well. I have not heard of that being the case, so should this warning be removed?
I strongly disagree with the NuGet plan, as having https on some types of internal networks is completely pointless and just causes extra overhead and work. For example, there is no point in setting up https for a localhost repository, or on an offline LAN network (both of which I have used), and for both of which it can be difficult to get a trusted certificate setup and working.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
With Chocolatey CLI v2.2.2 (well all v2.x versions I think), when pushing to a http source, a warning from the NuGet assemblies is shown:
[NuGet] You are running the 'push' operation with an 'HTTP' source, 'http://nexus.repo/repository/choco/'. Non-HTTPS access will be removed in a future version. Consider migrating to an 'HTTPS' source.
This warning can be read as Chocolatey moving to having https everywhere as well. I have not heard of that being the case, so should this warning be removed?
This warning is from the NuGet assemblies as they are moving to require https everywhere:
https://devblogs.microsoft.com/nuget/https-everywhere/
I strongly disagree with the NuGet plan, as having https on some types of internal networks is completely pointless and just causes extra overhead and work. For example, there is no point in setting up https for a localhost repository, or on an offline LAN network (both of which I have used), and for both of which it can be difficult to get a trusted certificate setup and working.
Beta Was this translation helpful? Give feedback.
All reactions