Communications
by telecom or Internet would use dynamic encryptions to protect its contents.
The encryption algorithms don’t use a master decryption key, but dynamically
changed encryption/decryption key.
The
idea was from telecom technology in authentication. Telecom system authenticates
a mobile phone using authentication by RANDU, SSD, and CAVE. We would use an SSD
as a dynamic key to encrypt/decrypt a packet.
B.
Internet and Telecommunications
1.
Https
Currently
we’re using https as an encryption technology in many countries, i.e. shared
encryption technology.
2.
Encryption
The
issue was that there were not many encryptions available for many important
organizations or general public use in telecom or Internet communications. So,
computer industries would share a set of encryptions in many nations. Telecom
industry should share another set of encryption algorithms.
It’s
not easy to keep an encryption algorithm secret. The goal is to make hackers to crack any packets by running all cracking algorithms. This would take them
months or years to decrypt a packet. By the way, a short email would include
many packets, so hackers would be in trouble to decrypt an email.
3.
Common pool and private pool of encryption algorithm
If
there were many encryption algorithms, we could divide those in 2 pools of
encryptions. Roamers from another place would communicate with a local telecom
or Internet network by using the common pool of encryptions agreed by
regulators or industries.
Private
or local users could use either common pool or private pool of encryptions.
4.
Methodology or protocol
Let’s
assign the common pool of encryption by a unique version number or characters
agreed in the applicable industry.
a.
Common pool
-
The first communication message to an ISP or telecom network would
be encryption version.
-
If the roamer couldn’t understand the private (local) version of
encryption set, they would send a request to use the version of common pool.
-
The communication would then be in common pool’s algorithm.
Use
of private encryption pool could be done easily with a version number. If the name
of encryptions is changed, the version name would be changed, too.
b.
Same set of encryption, but different names
Even
hackers knew the encryption, but if they didn’t know which algorithm used in
encrypting a packet, they must run all decryption possible algorithms to
decrypt a packet, i.e. months or years to know the content of our message.
In
a previous note, a computer and ISP must exchange encryption names and protocol
to specify association of an encryption and a packet. This helps the ISP (or
telecom operator) to decrypt a message easily as required by laws.
The
key would be encryption names. If hackers didn’t know the encryption names,
they would be forced to run all decryption algorithms.
To
make decryption harder to hackers, we would change names of encryption
algorithm or software regularly. Each location (ISP or telecom operator) could
have different names for the same set of encryption algorithms. The protocol
could be as follows
-
The first communication
message to an ISP or telecom network would be encryption version or pool
version.
-
If the common pool of
algorithm was not available, the ISP would send a message to the user to
download encryption software with unique names as well as its version number.
Because
the whole industry only used a set of algorithms, thus let the user to download
the encryption software should be fine, i.e. the device knew algorithm in other
names.
C.
Changing encryption names
Regulators
or special teams could change names of encryptions or add new encryption
algorithms at any time. They only need to change version names and allow users
to download new encryptions.
No comments:
Post a Comment