-
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
Get-ChocolateyWebFile - Ensure PSVersionTable is used for PowerShell Version #1623
Comments
Whoops, looks like we were grabbing the wrong version there. Great find, looks good for a fix as well! |
ferventcoder
pushed a commit
that referenced
this issue
Sep 26, 2018
When determining the PowerShell version, using `$host.Version` is ill-advised - it is dependent upon the host and may not be an accurate value. In the case of Visual Studio Code, it was coming up with the version of VS Code and not PowerShell's version. This leads to unexpected behavior. Instead, to make a determination of the version of PowerShell, use `$PSVersionTable.PSVersion`. See this [link](https://blogs.technet.microsoft.com/heyscriptingguy/2014/10/13/powertip-check-version-of-powershell/) for more information.
ferventcoder
added a commit
that referenced
this issue
Sep 26, 2018
* pr1624: (GH-1623) Use PSVersionTable for Version
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
Sep 26, 2018
* stable: (chocolateyGH-1623) Use PSVersionTable for Version (doc) fix up doc mistakes (doc) update licensed changelog
This was merged into stable at d43e9fd and will go out in v0.10.12. Thanks again! |
ferventcoder
changed the title
Setting Security Protocol to ssl3 is not supported with PowerShell 6.0.3
Get-ChocolateyWebFile - Ensure PSVersionTable is used for PowerShell Version
Mar 13, 2019
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to run chocolatey with PSVersion 6.0.3 setting the security protocol to ssl3 raises the mentioned error here.
SSL3 is deprecated:
https://blogs.technet.microsoft.com/askpfeplat/2018/02/12/retire-those-old-legacy-protocols/
https://tools.ietf.org/html/rfc7568
https://docs.microsoft.com/en-us/security-updates/securityadvisories/2015/3009008
Steps to reproduce
Expected behavior
Actual behavior
Environment data
The text was updated successfully, but these errors were encountered: