Hi all,
The SSLv3/POODLE exploit has been getting a lot of play the past couple days. Has anyone run into trouble with their 2011/2013 deployments when trying to fix issue? I'm thinking this is more a problem for Claims/IFD deployments. The solution is to turn off
SSL3.0 and turn on TLS which from what I understand is turned off by default in Server 2008R2. Does CRM even care which is used? Also, the users would probably have to make sure that TLS is enabled in their browsers.
Anybody gone through this with their CRM deployment yet?
Thanks
Rob