TLS 1.2 issues on .NET 4.5 agents
jessehouwing opened this issue · 11 comments
It looks like the Microsoft tasks have "patched" the SecurityProtocol setting:
microsoft/azure-pipelines-tasks#6905
This means that every other task author must steal this file. Any chance this can be merged into the PowerShell Task Library and be auto-initialized?
Or can the agent perform this for each powershell execution handler initialization? It feels weird that it's a helper module in the tasks repo, instead of a proper fix in the agent or the lib.
This issue has had no activity in 90 days. Please comment if it is not actually stale
@damccorm the bot closed this even after Jesse responded to its comment request. Thoughts?
@stephenmichaelf what should we do here?
Hm, apparently stale doesn't respect comments (I had thought it did) - we can either remove the configuration for now or just manually unlabel any that come in like this. I get notifications for comments, so I can handle doing that for now.
Closing stale issues is great, wouldn't want to lose that. If it becomes a burden on you, then we could automate with another Action.
Closing stale issues is great, wouldn't want to lose that. If it becomes a burden on you, then we could automate with another Action.
Yeah, let's see. It looked like they wanted to fix the issue I linked to, so may be a non-issue. Worst case, I might follow up in that repo with a PR.
Hm, the bot was persistent here since we didn't remove the stale label. I think in theory we should pick up changes from the action itself to fix this automatically though, so lets see if the stale label gets removed automatically next time it runs
This issue has had no activity in 90 days. Please comment if it is not actually stale
@stephenmichaelf is this tractable for us to take in the lib? If so, we can talk offline about how to staff it.
This issue has had no activity in 90 days. Please comment if it is not actually stale