<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>tls 1.2</title><link>https://evotec.xyz/fr/tags/tls-12</link><description>Evotec Main Website</description><atom:link href="https://evotec.xyz/fr/tags/tls-12/index.xml" rel="self" type="application/rss+xml" /><item><title>PowerShellGallery disables support for TLS 1.0 breaking Install-Module</title><link>https://evotec.xyz/fr/blog/powershellgallery-disables-support-for-tls-1-0-breaking-install-module</link><description>A few days ago, I tried to use Install-Module on the old Windows 2008R2 system that I use for specific tasks.</description><pubDate>Thu, 09 Apr 2020 20:18:19 GMT</pubDate><guid>https://evotec.xyz/fr/blog/powershellgallery-disables-support-for-tls-1-0-breaking-install-module</guid><category>powershell</category><category>tls</category><category>tls 1.0</category><category>tls 1.2</category></item><item><title>Invoke-RestMethod : The underlying connection was closed: An unexpected error occurred on a send while connecting Graph API</title><link>https://evotec.xyz/fr/blog/invoke-restmethod-the-underlying-connection-was-closed-an-unexpected-error-occurred-on-a-send-while-connecting-graph-api</link><description>In the last few days, I’ve got two reports that my PowerShell module for Office 365 Health suddenly started giving errors. This was a bit weird because it worked perfectly fine on my end. But while I could understand one person having an issue of their own, with their network or firewalls, if the second person comes along with the same report, that means something else is going on.</description><pubDate>Sat, 14 Dec 2019 11:01:16 GMT</pubDate><guid>https://evotec.xyz/fr/blog/invoke-restmethod-the-underlying-connection-was-closed-an-unexpected-error-occurred-on-a-send-while-connecting-graph-api</guid><category>invoke-restmethod</category><category>office 365</category><category>powershell</category><category>tls 1.0</category><category>tls 1.1</category><category>tls 1.2</category></item></channel></rss>