https://dot.net now using TLS 1.2-only
- Dominant language
- No language data
- Stars
- 1.4k
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Earlier today, https://dot.net switched to using TLS 1.2-only. Most Windows Powershell instances default to TLS 1.1 and will thus fail with `wget : The underlying connection was closed: An unexpected error occurred on a send. trying to run the previous command.`
An example of a PowerShell script fix can be seen in https://github.com/dotnet/docs/pull/6689
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no file, test, or repository change. Start by reading the referenced dotnet/docs pull request 6689 and reproducing the failing PowerShell command against https://dot.net; done would require an agreed implementation target for TLS 1.2-only connections, which this issue does not define.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- networking, operating-systems, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100