Here are some specific encryptions of different types of messages exchanged between the
participating parties.
1. Shakespeare:
The famous lines from William Shakespeare's Romeo and Juliet:
'What's in a name? That which we call a rose
By any other word would smell as sweet.'
are considered a benchmark in encryption. So, let us see how they look in our encryption.
We will consider two encryptions, made seconds apart - one
in the Google Cloud, the other in Microsoft Cloud. We have to say right away
that neither one has anything to do with the Clouds Operations per se - they are simply 2 separate
documents for easier-to-distinguish presentations.
Here they are:
The fact that the time measured for the encryption process
itself is orders of magnitude faster than the competition is not important or
even relevant to the advantages of our encryption that we would like to emphasize.
But compare the 1st line of Google Docs with the 1st line of
Microsoft Word - they are completely
different, despite the fact that they encode
the same thing!
Same document, same paragraph, same line!
Completely different, yet decoded into the same text!
Now, this is something worth attention.
We have used the AES
encryption of the same benchmark text, to WRAP it up in our encoding and transfer it untouched through the
Mid-points.
Please, have a look at the Embedded Encryption submenu of 'Details' menu item.
Usually we expect timing around 1 millisecond, which is still orders of magnitude faster
than the best in the Old Encryption field.
We actually measure in microseconds, rather than in
milliseconds like most of the Old Methods do, in fact. We expect a timing of
1,000 microseconds, rather than 100 microseconds.
The 'aaaa...' message has timing
that is an order of magnitude lower than the average we would expect. Just
keep this in mind.
You also have noticed that the timing between 2 runs is NOT
the same. This is because we run along with other processes, and we mean background processes, dozens of them.
BOTH the
background processes and the fact that our measure is so low (microseconds)
contribute to these differences. Timing also depends on how many functions you use
from our manipulation library (currently standing at 14).
So, let's wrap-it-up in our encryption and see how the '2 in 1' will look like - notice that hexadecimal encryption, or AES encryption,
or plain text encryption look identical for our wrapping.
We don't know what the naked Bitcoin message is.
We don't know how strong THEIR encryption is. All we care about is the message to arrive at the other end the SAME,
undisturbed and untouched going through the Mid-Points. That's the goal of '2 in 1' wrapping.
You have probably read the recent article "Crypto Confidence Ebbs" - proper encryption
or the lack of it, is a good part of this ebb, we think. Wrapping it in our '2-in-1' encryption is
an easy and natural solution, you would agree we'd think.
Our parent company has different IoT Clients, but by far the most important IoT
in our view are the Medical Devices IoT.
The naked text is a bit strange for outsiders, but Cyber Confidential wrapping
doesn't make any difference anyway because our task is to deliver the cipher to
the other end undisturbed and untouched.
So let's see how we can wrap a medical information taken from NIST itself:
Here is the encryption in Cyber Confidential of these 2 lines of NIST medical data:
Again we have no idea what the other side is going to do with this data - our mission of delivering the message to EndPoint2 untouched and undisturbed is accomplished.
'Experts say it doesn't matter if Congress breaks up Facebook -
the company already has all of your data'
(In the comments below, by 'THEY' or 'COMPANY' we DO NOT MEAN Facebook or any other particular company.)
If a company doesn't encrypt in the beginning, while later they offer encryption BUT THEY KEEP the Keys
(virtually every company still uses Encryption Keys since in general companies
are slow-moving), that is something to be worried about.
You don't own anything, actually:
- Neither the encrypted message,
- Nor the necessary keys for your data to be
encrypted / decrypted,
- Not even the naked message since the Service
Provider needs it (and indeed has it) in order to encrypt your stuff!
Yes, you do have an identical copy of the naked message - but that is not a lot.
Please see the last topic "Cloud" under
the "Comparisson" menu to see
how Google handles this issue in the Google Workspace - this is something different!