#Cryptocat lates version cracked

The announcement was apparently a reaction to Steve Thomas’ own blog post in which he urged users who used Cryptocat from October 17th, 2011 to June 15th, 2013 to assume their messages were compromised. Of course, it does not in any way save from the fact that due to our blunder, seven months of conversations were easier to crack,” they explained, and apologized for making the mistake. All Cryptocat data still passed over SSL, and that offers a small layer of protection that may help with this issue. To the best of our knowledge, this is not the case. “Our SSL keys are safe: For some reason, there are rumors that our SSL keys were compromised.

Their security was not weakened,” they also made sure to note. “Private chats are not affected: Private queries (1-on-1) are handled over the OTR protocol, and are therefore completely unaffected by this bug.

#Cryptocat lates version cracked

A critical security vulnerability in Cryptocat versions older than 2.0.42 has been patched and developers are urging users to update to the latest available version of the encrypted online chatting app.Īccording to their Thursday blog post, the vulnerability was discovered by a volunteer named Steve Thomas a few weeks ago, and allowed any conversations had over Cryptocat’s group chat function between versions 2.0 and 2.0.42 to be easily cracked via a brute force attack.