Windows Server 2022上IIS的FTPS无法启用TLS 1.3问题咨询

我们在Windows Server 2022的IIS上无法为FTPS启用TLS 1.3。IIS的FTPS已正常运行多年，已知它依赖Windows Server的Schannel组件提供SSL/TLS支持，而Windows Server 2022原生支持TLS 1.3，且同服务器上的标准HTTPS Web应用已成功启用该协议。

环境配置 #

• 服务器系统：Windows Server 2022标准版
• 已部署包含FTP功能的IIS角色
• 已禁用TLS 1.0和1.1，完成FTPS及Web服务器的基础配置

扫描结果验证 #

FTPS服务（990端口）nmap扫描结果 #

仅支持TLS 1.2：

PORT    STATE SERVICE VERSION
990/tcp open  ssl/ftp Microsoft ftpd
| ssl-enum-ciphers:
|   TLSv1.2:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp384r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (ecdh_x25519) - A
|       TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (dh 2048) - A
|       TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (dh 2048) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (secp384r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (secp384r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_RSA_WITH_AES_256_GCM_SHA384 (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_GCM_SHA256 (rsa 2048) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA256 (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA256 (rsa 2048) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
|     compressors:
|       NULL
|     cipher preference: server
|     warnings:
|       64-bit block cipher 3DES vulnerable to SWEET32 attack
|_  least strength: C
Service Info: OS: Windows; CPE: cpe:/o:microsoft:windows

同服务器HTTPS应用（443端口）nmap扫描结果 #

支持TLS 1.3：

PORT    STATE SERVICE
443/tcp open  https
| ssl-enum-ciphers:
|   TLSv1.2:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp384r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (ecdh_x25519) - A
|       TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (dh 2048) - A
|       TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (dh 2048) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (secp384r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (secp384r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_RSA_WITH_AES_256_GCM_SHA384 (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_GCM_SHA256 (rsa 2048) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA256 (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA256 (rsa 2048) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
|     compressors:
|       NULL
|     cipher preference: server
|     warnings:
|       64-bit block cipher 3DES vulnerable to SWEET32 attack
|   TLSv1.3:
|     ciphers:
|       TLS_AKE_WITH_AES_256_GCM_SHA384 (secp384r1) - A
|       TLS_AKE_WITH_AES_128_GCM_SHA256 (ecdh_x25519) - A
|     cipher preference: server
|  least strength: C

服务器可用加密套件列表 #

通过PowerShell命令Get-TlsCipherSuite | Format-Table Name输出：

PS C:\Users\Administrator> Get-TLsCipherSuite | Format-Table Name
Name                                   
----                                   
TLS_AES_256_GCM_SHA384                 
TLS_AES_128_GCM_SHA256                 
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384  
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256  
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384    
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256    
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384  
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256  
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA   
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA   
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA     
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA     
TLS_RSA_WITH_AES_256_GCM_SHA384        
TLS_RSA_WITH_AES_128_GCM_SHA256        
TLS_RSA_WITH_AES_256_CBC_SHA256        
TLS_RSA_WITH_AES_128_CBC_SHA256        
TLS_RSA_WITH_AES_256_CBC_SHA           
TLS_RSA_WITH_AES_128_CBC_SHA           
TLS_RSA_WITH_3DES_EDE_CBC_SHA          
TLS_RSA_WITH_NULL_SHA256               
TLS_RSA_WITH_NULL_SHA                  
TLS_PSK_WITH_AES_256_GCM_SHA384        
TLS_PSK_WITH_AES_128_GCM_SHA256        
TLS_PSK_WITH_AES_256_CBC_SHA384        
TLS_PSK_WITH_AES_128_CBC_SHA256        
TLS_PSK_WITH_NULL_SHA384               
TLS_PSK_WITH_NULL_SHA256

问题 #

请问IIS的FTPS是否不支持TLS 1.3，或是存在其他配置问题导致无法启用？

更新于2024-07-02：目前发现大量用户遇到相同问题，需要TLS 1.3时多选择第三方FTPS服务器软件替代IIS FTPS，我们也正基于跨平台兼容性及功能需求探索使用SFTPGo。

内容的提问来源于Stack Exchange，提问作者Henrik Bo Christensen