For many MANY years, there has been a need to hide communications from others. Over the years, there have been many ways to encrypt a message. You have, in the “old school”: one time pads, CodeBooks, offsets, etc. In the “new school” we have: XOR, Public/Private Key systems of many flavours, etc. We also have “supposedly” encrypted services we can buy (or free versions) of things such as Signal (I like this one the best), Session, WhatsApp (VERY BAD!), Wickr, Viber, and many, many more.
The problem with the “instant” messaging, someone else controls the software, and while they say it is secure, I have seen time and time again, where that is not always the case, especially with WhatsApp.
The best encryption process I have seen over time is a CodeBook process. As long as the code book isn’t comprimised (and that is normally done by bad actors on “your team” releasing it to the wild.
Here at Secure Computers Solution Company we have a new twist on the CodeBook system that makes it even better. At this point the system isn’t an instant messaging system (and may never become so), but is a file based system in which you create your message on your computer, soon your phone as well, encrypt it using a CodeBook from a list of CodeBooks you have in your account, and then it a second encryption from another process we’ll keep to ourselves. You then email that message to the recipient that has the same CodeBook and they are then able to decrypt both layers and read the note.
In this process we have two applications. The first is CBManager. This application allows you to build as many CodeBooks as you want. Let’s play some examples here. Let us say you are in a highly competitive business that has a Sales Team, Marketing Team, Development Team and a Management Team. The Manager of the CodeBooks (or head of Sales, Marketing, etc.) then Creates the Sales (5 characters for the name at all times) CodeBook, then the Markt CodeBook, Devel CodeBook, and Manag CodeBook and distributes the individual teams their CodeBooks. (S)He may one to do one for the whole company, say _SCSC and give it to everyone.
Now each user has the second application CBClient and imports the CodeBook(s) they receive. (CBManager can import CodeBooks from other CBManager applications as well.) Anyone with the CodeBook the message was written into can read the message, but the CodeBooks do not travel around once given to a person, so the security of same is string.
With the double layer of encryption, the decryption by bad parties is near non-existent.
