大网数据广告活动
服务器运维问答

Why is TLS1.0 still seemingly supported on a "minimum TLS1.2" web app service on azure?

· 52CE 我爱测

We have an app service on Azure, and as Microsoft made available recently (april 30 2018), we now have an option to require TLS 1.1 or 1.2 : We run hackerguardian scans for PCI compliance, yet, they still return failure on TLS su…

问题原文

原帖链接 · Kraz · CC BY-SA 4.0

We have an app service on Azure, and as Microsoft made available recently (april 30 2018), we now have an option to require TLS 1.1 or 1.2 :

We run hackerguardian scans for PCI compliance, yet, they still return failure on TLS support :

I also ran the ssl test from ssl labs. And result were... unclear :

There are no TLS 1.0 Cypher in the Cypher suites section, and all handshake simulation use TLS 1.2

Finally, if I try to open the app in IE with TLS 1.2 disabled, it fail :

I am unsure about what to try next. My guess is that TLS1.0 is still supported but with no cypher, so all connection attempts fail. Any other way to test TLS1.0 support, beside my IE test?

已采纳解答

原帖链接 · Kraz · CC BY-SA 4.0

It's caused by a feature is done, but not done-done issue. More information is available from Microsoft. As of today (June 19th), there are still some edge cases that are not handled correctly. Full support is now delayed to the beginning of July (after the PCI Compliance date).

(May 14th)

This is actually working at the moment in blocking TLS 1.0, but the reports are catching an unsupported edge case which are deploying a fix for most likely by the end of the week. Reports like SSL Labs are marking TLS 1.0 in orange as is blocked, but not complete.

This issue is documented here:

https://blogs.msdn.microsoft.com/appserviceteam/2018/05/02/breaking-change-for-sni-ssl-hostnames-on-azure-app-service/

(May 21th)

This was delayed a bit, deploying right now and will be live in full during the first week of June, though some may see this update sooner.

(June 14th - someone asked)

TLS 1.0 is showing as being removed from port 443. Thank you.

However, an nmap scan still shows that port 455 has TLS 1.0 and TLS 1.1 enabled.

Could you please confirm that you're aware of this and are working on removing TLS 1.0 from port 455 as well?

(June 14th - the answer)

@anotherazureuser - the solution for that specific port will be deployed in 2-3 weeks. Stay tuned.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2018-05-09)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。