miracle091/Picocrypt
miracle091
/
Picocrypt
mirror of https://github.com/HACKERALERT/Picocrypt.git
1
0
Fork 0
Code Releases Activity

Update Changelog.md

This commit is contained in:
Evan Su 2021-08-02 09:50:32 -04:00 committed by GitHub
parent 81351f86fb
commit 257a18b9db
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Changelog.md
View File

@ -1,19 +1,21 @@
# v1.15 (future) # v1.15 (future)
<ul> <ul>
<li>Add cancel button to file shredder</li> <li>Add cancel button to file shredder</li>
<li>Password generator</li>
<li>Localization support</li>
</ul> </ul>
# v1.14 (ETA: ~ 16 days) # v1.14 (ETA: ~ 16 days)
<strong>v1.14 will unfortunately be incompatible with v1.13, as I have dropped Poly1305 in favour of an HMAC. Because I have appended the encryptor version to the encrypted data in v1.13, however, v1.14 and on will be able to tell you which version your data was encrypted with so that you can fetch the correct verion of Picocrypt. There are no security issues in any previous versions of Picocrypt as long as you use a strong password.</strong> <strong>v1.14 will unfortunately be incompatible with v1.13, as I have dropped Poly1305 in favour of an HMAC. Because I have appended the encryptor version to the encrypted data in v1.13, however, v1.14 and on will be able to tell you which version your data was encrypted with so that you can fetch the correct verion of Picocrypt. There are no security issues in any previous versions of Picocrypt as long as you use a strong password.</strong>
<ul> <ul>
<li>Low-severity security fix for the recently discovered <a href="https://eprint.iacr.org/2020/1491.pdf">partitioning oracle attacks</a></li> <li>Low-severity security fix for the recently discovered <a href="https://eprint.iacr.org/2020/1491.pdf">partitioning oracle attacks</a></li>
<li>Move from Monocypher to Go's standard supplemental ChaCha20 in favour of being stateful</li> <li>Move from Monocypher to Go's standard supplemental ChaCha20 in favour of being the latter being stateful</li>
<li>Removed ~100 lines of unnecessary code now that Picocrypt uses Go's ChaCha20 (cleaner and stabler code)</li> <li>Removed ~100 lines of unnecessary code now that Picocrypt uses Go's ChaCha20 (cleaner and stabler code)</li>
<li>Added window icons</li> <li>Added window icons</li>
<li>Switch to a new Reed-Solomon encoder that automatically corrects errors</li> <li>Switch to a new Reed-Solomon encoder that automatically corrects errors</li>
<li>Add a "Paranoid mode", which will use the Serpent cipher in addition to ChaCha20</li> <li>Add a "Paranoid mode", which will use the Serpent cipher in addition to ChaCha20</li>
<li>Cleaner code with plenty of comments for people taking a look</li> <li>Cleaner code with plenty of comments for people taking a look</li>
<li>Metadata is now Reed-Solomon encoded (everything bit of header data such as nonces and Poly1305s are RS-encoded)</li> <li>Metadata is now Reed-Solomon encoded (everything bit of header data is now RS-encoded for redundancy)</li>
<li>Reed-Solomon checkbox is now enabled and Reed-Solomon works</li> <li>Reed-Solomon checkbox is now enabled and Reed-Solomon works</li>
<li>Implemented Dropbox's zxcvbn password strength checker</li> <li>Implemented Dropbox's zxcvbn password strength checker</li>
<li>Removed paranoid shredding as it is too hard to implement correctly and not cross platform</li> <li>Removed paranoid shredding as it is too hard to implement correctly and not cross platform</li>
@ -23,7 +25,7 @@
<li>Advanced options are shown dynamically depending on whether encrypting or decrypting</li> <li>Advanced options are shown dynamically depending on whether encrypting or decrypting</li>
<li>Window closing disabled during encryption/decryption/shredding to prevent leakage of temporary files</li> <li>Window closing disabled during encryption/decryption/shredding to prevent leakage of temporary files</li>
<li>Improved user flow as well as fix UI bugs</li> <li>Improved user flow as well as fix UI bugs</li>
<li>Code optimizations, better commenting, cleaner code</li> <li>Code optimizations</li>
<li>Many bug fixes/stability improvments</li> <li>Many bug fixes/stability improvments</li>
</ul> </ul>