I have an existing integration with Twilio that works great - Twilio posts a message to a custom SFDC REST endpoint, and we can generate a new SMS message by calling out to the standard Twilio REST API.
Yesterday, I received an email referencing this security alert, which states that Twilio will be removing support for SSLv3, and requiring any platform interacting with Twilio to use TLS:
For customers only supporting SSLv3 for inbound HTTP requests from Twilio, we plan on discontinuing this service on 22 October 2014 at 9am PDT / 1600 UTC. Customers with applications that only support SSLv3 are encouraged to upgrade to TLS as soon as possible, as SSLv3 will be unavailable on that date.
Does anyone know if this will break my current integration? To my knowledge, I have never set an option regarding the method of Secure Transport anywhere for inbound or outbound posts - I just set the endpoint, and it worked fine. Is there so way to test it in a Sandbox/Dev system? I am struggling to find anything in documentation to even know if this will be an issue.