Taking advantage of an algorithm similar to that of CRIPTEOS 3001, also patented, we have the use of a 12,000 byte long key, so even in this case we are at levels of security that are vastly superior to that of current algorithms. However, the short key technically requires doubling the length of the message when it is encrypted. What might have seemed like a flaw has become a strong point of KEY-LOCK, which stores encrypted passwords. The plaintext password can only be seen on the PC monitor while encrypted is stored on the hard disk. But as a simple secure password KEY-LOCK also becomes a defender of its data when accessing institutional or private sites with a user account and a password. Generally passwords are easily obtained from information on social networks, such as Facebook etc. Names of children, dates, simple combinations and the HACKER, with the technique called SOCIAL ENGINEERING finds the password very quickly. With KEY-LOCK it’s different. Let’s say that our INPS password is MARIO1987. KEYLOCK converts it into a string of characters that is twice as long and generated with algorithms, therefore without any support for SOCIAL ENGINEERING. Just replace in the computer system, for example that of the INPS, the new string with MARION1987 and the security of our access to this site is greatly enhanced. We still on the monitor that shows the KEY-LOCK software we continue to see MARION1987, but only there.
Now most sites claim a secure password and there are sites to show an algorithmic password to defend.
But the problem is how to keep the pssword and people memorize the password in the site. Wrong!
The advantage of our system is that customer view the mnemoric password in the monitor
and copy and paste the algorithmic password in the site access.