[JIRA] (JENKINS-49725) Windows SSH init broken, as of 2018-02-22
Title: Message Title Oleg Nenashev resolved as Fixed Marking as Fixed according to the comment Jenkins / JENKINS-49725 Windows SSH init broken, as of 2018-02-22 Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49725) Windows SSH init broken, as of 2018-02-22
Title: Message Title Ken Chen commented on JENKINS-49725 Re: Windows SSH init broken, as of 2018-02-22 Fixed in v0.6.2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49725) Windows SSH init broken, as of 2018-02-22
Title: Message Title Chenyang Liu assigned an issue to Chenyang Liu Jenkins / JENKINS-49725 Windows SSH init broken, as of 2018-02-22 Change By: Chenyang Liu Assignee: Azure DevOps Chenyang Liu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49725) Windows SSH init broken, as of 2018-02-22
Title: Message Title Chenyang Liu commented on JENKINS-49725 Re: Windows SSH init broken, as of 2018-02-22 Thanks, we will fix it immediately. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49725) Windows SSH init broken, as of 2018-02-22
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-49725 Windows SSH init broken, as of 2018-02-22 Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2018-02-24 02:16 Priority: Critical Reporter: Jo Shields GitHub has turned off support for TLS versions before 1.2, on all of https://github.com - https://githubengineering.com/crypto-removal-notice/ The Azure VM Agents plugin hardcodes a URL on github.com in its Windows SSH init script, and downloads it using System.Web.WebClient - https://github.com/jenkinsci/azure-vm-agents-plugin/blob/0e57250114b29b14ae787928b6debeafbf9d67ff/src/main/resources/scripts/sshInit.ps1#L3 Unless directed otherwise, PowerShell will always use TLS 1.0 - https://blog.pauby.com/post/force-powershell-to-use-tls-1-2/ As a result, initialization of Windows SSH agents is 100% broken, as of yesterday, because the sshInit.ps1 script does not override the TLS version on WebClient to 1.2, causing the script to fail. This cannot be worked around, without a custom compile of the plugin with a fixed PowerShell script. Add Comment
