Oversec Help

Encoding

Oversec provides multiple methods of encoding an encrypted message:

Invisible (Decoy) Encoding

This unique method encodes the encrypted text as invisible (zero width) characters at the beginning of the text. The text is then padded with decoy content to make sure that the receiving device provides enough screen-space to render the decrypted

When entering or editing the decoy text, a border is drawn around the input field. The border color will turn red if the decoy text is too short and there will probably not be enough screen space on the receiving device to show the decrypted text. The border color will turn green if enough decoy text has been entered.

When editing the decoy text, it may happen that you accidentally delete parts of the invisible encrypted text. If this happens, Oversec will show an error and you will have to start over! (There is no way to recover the plain text!)

Some Apps limit the number of characters that can be written back into an input field and crash or freeze when Oversec tries to write back the encoded text to the app. There's unfortunately nothing we can do about this, other than that you need to use a different encryption method or encoding:

BASE64-Encoding

This encodes the encrypted text as a series of printable characters, guaranteed to work with all apps and systems.

This is mainly intended for use with symmetric encryption for legacy SMS text messages.

Ascii-Armoured PGP

This is only available for PGP encoded messages and encodes them as a "ascii armoured" string.

Symmetric Encoding vs. PGP Encoding

PGP encoding produces much more data than symmetric encryption. Please use symmetric encoding if data length is a concern!