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
ferventcoder
changed the title
If switch down to SSLv3 doesn't work, switch back
For PowerShell v2 - if switch down to SSLv3 protocol fails, go back to original
Sep 12, 2016
When original protocol fails in PowerShell v2, `Get-ChocolateyWebFile`
will switch to try the older SSL v3 protocol. When that also fails, the
original protocol should be reinstated.
* 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
...
In PowerShell v2, sometimes the protocol switches down to get files. If that still has issues, switch back to the original security protocol
The text was updated successfully, but these errors were encountered: