We have just released a hotfix for Secure Chat that resolves a number of important issues on top of the previous version, delivering greater convenience.
The new release of Secure Chat makes possible adding contacts from multiple sources to the app’s contact list and keeping them all organized in one place.
The new version of Secure Chat is finally here! We can proudly say that it is one of the most significant releases in the past few months as it is focused on stability and fine-tuning. Version 2.1.2 brings critical bug fixes in the area of data and battery consumption and self-destructing messages.
We’ve always tried to keep behind the scenes the complex encryption processes that guarantee secure communications to our users and only present security solutions that are easy and intuitive to use. In another step towards that goal, Secure Group is excited to introduce Security Lock – a single passcode for app lock and data encryption that unifies the flow for our flagship applications. It makes its big debut in Secure Chat v2.1.0, and will soon be incorporated in Secure Email and other major applications on Secure Phone.
If you care about your privacy, you need to use apps that provide end-to-end encryption for your communications. Providing this kind of security for group chats is a technical challenge. The OMEMO extension for XMPP, which Secure Chat also uses, solves this challenge with the Double Ratchet Algorithm. Here is how it works.
We’re pleased to announce a major upgrade to Secure Chat. Version 2.0 is the biggest upgrade to date, adding voice and video calling, and introducing Group Chat feature.
A few choice tweaks and a raft of bug fixes in the latest Secure Chat v1.12.0 makes for a more intuitive and more stable user experience.
The latest release of Secure Chat focuses on backend improvements, providing for better stability and a better user experience. Joining Secure Email, Secure Chat also sports the “new look” icon that’s rolling out across the range of Secure Pack apps.
All chat apps rely on servers over which end users have no control. How do you guarantee the user's privacy then? For our proprietary IM client, Secure Chat, we have done it by making the app a pure peer-to-peer (P2P) encrypted chat client and by limiting the role of the servers to just facilitating the communication.
Google announced last month the first ever collision generated in the SHA-1 cryptographic hashing algorithm. Or to paraphrase it – SHA-1 is not secure anymore. Truth be told, theoretical flaws in the algorithm were known for a long time. And this is why Secure Group has already moved on to SHA-2 for the implementation of Off-the-Record (OTR) encryption in our proprietary chat client, Secure Chat. But what does SHA-1’s demise mean for cryptography and security?