Last night TokBox released patches to the OpenTok iOS and Android SDKs to resolve a recently identified OpenSSL vulnerability that affects the majority of web service providers.
In early June, a security advisory was issued by OpenSSL, quoting the following:
‘An attacker using a carefully crafted handshake can force the use of weak keying material in OpenSSL SSL/TLS clients and servers. This can be exploited by a Man-in-the-middle (MITM) attack where the attacker can decrypt and modify traffic from the attacked client and server.’
As an OpenTok customer, you know that in order to deliver a great call experience, network connectivity is king. You can spend hours developing your real-time communications app, only to encounter connectivity hurdles like corporate firewalls or blocked IP in a new network environment.
It’s important to know that your application will work where you need it to, whether you’re pitching an investor, selling to a client, or just showing off all your hard work. That’s why we’re excited to launch the first version of the OpenTok Connectivity Doctor.
The OpenTok Connectivity Doctor helps you diagnose problems with your network before or after you connect to an OpenTok session. This tool does not test for errors in your code.
With our fourth WebRTC Conference & Expo now a week behind us, we wanted to take some time to reflect on the event. There was never a dull moment for Team TokBox in Atlanta. We gave a keynote address, participated in several panel discussions, gave a live demo of our video driver and manned our bustling booth complete with a Bridgestone Golf B-FIT kiosk.
Hot off the heels of our OpenTok 2.0 Archiving API pricing and storage announcement we’re excited to announce that our Archiving API has now gone into production.
You can find out more about the features of this API in our previous post or by taking a look at our docs page and here is a quick summary just in case:
Following on from our OpenTok archiving and storage announcement we’re excited to fill you in on some updates we are making to our OpenTok iOS and Android SDKs 2.2 that are going into production. What started out as internal engineering project has paved the way to the release of a suite of valuable mobile features which have become a formal part of the product offering, setting OpenTok further apart from other WebRTC platforms.