From 42b5137c08419256853e857a32e6bd596deddfd8 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Tue, 16 Mar 2021 09:50:31 -0400 Subject: [PATCH] Added Reed-Solomon description --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index ee68c0d..966f0d8 100644 --- a/README.md +++ b/README.md @@ -28,6 +28,7 @@ Picocrypt is about as simple as it gets. Just select a file, enter a password, a
  • File metadata (editable for encryption, readonly for decryption): Use this to store notes, information, and text along with the file (it won't be encrypted). For example, you can put a description of the file before sending it to someone. When the person you sent it to selects the file in Picocrypt, your description will be shown to that person.
  • Keep decrypted output even if it's corrupted or modified (decryption only): Picocrypt automatically checks for integrity upon decryption. If the file has been modified or is corrupted, Picocrypt will delete the output. If you want to keep the corrupted or modified data after decryption, check this option.
  • Securely erase and delete original file (encryption only): If checked, Picocrypt will generate pseudo-random data and write it to the original file while encrypting, effectively wiping the original file. The file will be deleted once encryption is complete.
  • +
  • Prevent corruption using Reed-Solomon (encryption only): This feature is very useful if you are planning on archiving important data on a cloud provider or external hard drive for a long time. If checked, Picocrypt will use the Reed-Solomon error correction code to add 8 extra bytes for every 128 bytes to prevent file corruption. This means that up to ~6% of your file can corrupt, and Picocrypt will still be able to correct it and decrypt your files with no corruption.
  • # Security