Your example answers a question I had about how this would actually be used, and it certainly is much more secure than I had initially assumed. However, it requires that your correspondent update their database every time you send a message. Yes, you can send your encrypted messages in the open but they will be logging in to the secure FTP site anyway. Why not just deliver the messages that way and skip the whole encrypt/decrypt? You will save a lot of time and effort.
There is a sound basis for NOT sending your messages in the open, even encrypted. Historically, a great deal has been revealed by learning who is talking to who, and the timing of their messages, without reading a word of the plaintext.
Your challenge to decrypt a message is truly childish, and demonstrates a poor understanding of the topic. Those methods only work on a body of data, not 1 or 2 messages.
In reply to Re^3: Non-Formula based Text Encoding - with Compression
by GotToBTru
in thread Non-Formula based Text Encoding - with Compression
by locked_user erichansen1836
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |