Noel_C__180670
Dec 20, 2014Nimbostratus
TLS1.x Padding Vulnerability Workaround and EAS
Hello, I'd like to employ the workaround described in SOL15882 where I'll have to create a custom cipher string using RC4-SHA ciphers. The SOL states "clients that do not support the RC4-SHA cipher will fail to establish a connection to the virtual server". Our virtual server is where our Exchange Active Sync (EAS) clients connect to. I would like to know which EAS clients, if any, would be impacted by this change. Any advice would be greatly appreciated!