|
Enter any two strings of the same length into each of the Lock and Key fields. These two strings combined will encrypt the message you enter into the input field (labelled Input your text). Press Encrypt to code your message. The recipient of your message must enter the same two strings into the Lock and Key fields, enter the encoded message into the input field, and press the decrypt button to read your message in the results field. Check here to en/decode unicode text. Check here to retain control codes eg 'newlines'. Your reader must also check these boxes to correctly decode any encoded messages. |
Input your text: |
||
|
Lock Key The Lock and Key values are not included in the message. You must give them to your reader, but not with your message or others may be able to read it. |
|||
|
Simple examples of the lock and key are shown, and sample text which contains both the original text and the encrypted text. Press both the encrypt and decrypt buttons to see what happens. Then write your own message. It is strongly recommended that you check that you can successfully decode your message before you send it. Enter the encoded message into the input area, and press Decrypt. Just a hint: spaces matter. If you get nonsense when you decrypt, then a space may be missing, or have been entered incorrectly. |
If a message fails to decode, it may be too long. Though in theory you are permitted to have up to 9 billiard characters it is likely that your PC will run out of memory, and you will run out of time if you try to decrypt a message as long as that. At 200 characters per minute you can only type 100 million in a year. Had Adam lived he would have been able to type about 900 milliard characters up to today, which is still only a myriadth part of the maximum length. Another possible cause is a lack of line breaks. Coco does not know why this happened, but a particular unicode encoded message of 2062283 characters without line breaks failed. The same message encoded as ansi was fine, as was the same unicode message when line breaks were retained. |
||
| Privacy notice: This page has no cookies. The lock and key texts and any data entered into the input field is neither sent to the server nor retained except on your own device in your own browser cache. Should you wish that nothing be retained, then consider using a private or incognito mode in your browser, or appropriately clearing your cache. Copyright © Stuart Moffatt 2016-2021 |
|||