<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>unsupported on Why did IT fail</title><link>https://www.why-did-it.fail/categories/unsupported/</link><description>Recent content in unsupported on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><lastBuildDate>Fri, 22 Sep 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/categories/unsupported/index.xml" rel="self" type="application/rss+xml"/><item><title>Thanks to U3</title><link>https://www.why-did-it.fail/blog/2023-03-vcenter8-ciphers/</link><pubDate>Fri, 22 Sep 2023 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2023-03-vcenter8-ciphers/</guid><description>Update on 2024-08-15:
Good news, with vSphere 8 update 3 the previous content became obsolte and I decided to take it offline and adjust the content here
Update 3 contains some major enhancements which makes the life in this regards much easier:
Starting in 8.0 Update 3, vSphere supports TLS 1.3 and 1.2 through the use of TLS profiles. TLS profiles simplify the job of administering TLS parameters and also improve supportability.</description></item></channel></rss>