For same strong password, the UID must be unique for each encryption. That is, the password and UID combination must be unique for each encryption and password must be very strong. Nothing is sent to the server. To test this, switch off the internet and encryption/decryption will still work in the browser. The standalone working html file can also be downloaded
and can be used offline in a good web browser. Please check the hash sum before using the offline copy.
HMAC-SHA-512 is derived from the password key, UID data and then XORed to the message.
Very Strong, provided UID is really unique for each encryption and password is strong.
Smallest base64 encoded cipher, easy to handle by humans for hand written text.
Good for small Messages.
All ATX keyboard characters. Do not use unicode or other keyboard characters.
(For password: pwd)
Date: 2018-08-23 00:32
As informed by you I will reach the venue 1#MHU0F+E= on 2#0vdjYsduCRmUAg== . I shall also accompany 3#M33GTtI= . We shall then decide our next 4#wsfxOD4EB2u31YGYoA== .
See you till then.
Date + counter will be used as UID after converting to 20180823 0032. Random Number between 2401 & 9999 can be generated if time is not known
Counter will start from 1.
Counter#Cipher will help decode message.
Since, the encrytped message is base64 formatted, it contains only A-Z a-z 0-9 + and / keyboard characters.
CAUTION! Epoch must be used for immediate time only. Epoch is for one block of plain text only (no counter). Device must be in sync to the Internet time. At least 1 second must pass before next XOR. Same device must be used OR half an hour gap. Epoch format: "epoch_value#cipher" (without quotes).