-
Notifications
You must be signed in to change notification settings - Fork 905
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
Attempt to download packages via HTTPS connection #746
Comments
@lennartb- one thing we've enforced is package checksum now for HTTP. I think we can also attempt to do this as well, which will make things better. |
This will ease things up a bit for some existing packages. It will attempt to determine if HTTPS is available and then use it to download instead. |
ferventcoder
added a commit
that referenced
this issue
Sep 12, 2016
If the host can be addressed with HTTPS, switch the download url to use HTTPS.
ferventcoder
added a commit
that referenced
this issue
Sep 12, 2016
* stable: (24 commits) (GH-839) Switch to apply package parameters to dependent packages (maint) formatting methods / parameters in calls (GH-958) If SSLv3 in Posh v2 Fails, Use Original (GH-746) Use HTTPS if available when HTTP url (GH-957) Skip Get-WebFileName When FTP (GH-948) Ensure passwords / keys are not logged (GH-952) Get-ChocolateyWebFile enhancements (doc) update generated docs (maint) formatting (docs) move GenerateDocs.ps1 / update (GH-932) Do not set unknown checksum to 'md5' (GH-719) Reset ServerCertificateValidationCallback (GH-305) add MSP/MSU installer types (GH-305) update exitcodes to long (GH-954) Pending fails when lib does not exist (GH-950) Install-ChocolateyPackage - UseOriginalLocation (maint) formatting (GH-922) Automatically determine checksum type (maint) fixes for shimgen (GH-948) Do not log sensitive arguments ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Split from #350
Trying to download certain packages with a HTTP-URL may fail in certain circumstances where for example a firewall blocks download of "insecure" files. Downloading a file via a HTTPS link however may work in that case. While the package URLs are of course dependent on the package maintainer, some server actually also serve via HTTPS besides HTTP.
Besides that HTTPS is more secure (though I can can't say whether this is interesting for choco), it would be convenient to either first try a HTTPS connection before HTTP, or add a flag (e.g. --TryHttps) which tries to force a download via HTTPS.
The text was updated successfully, but these errors were encountered: