1
0
Fork 0
mirror of https://github.com/HACKERALERT/Picocrypt.git synced 2024-12-28 10:24:19 +00:00

Cleanup, better formatting

This commit is contained in:
Evan Su 2022-05-08 19:52:55 -04:00 committed by GitHub
parent 2f015f40d3
commit 5ffd75b360
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -30,7 +30,7 @@
# v1.26 (Released 04/18/2022)
<ul>
<li>✓ <strike>Fix race conditions, running `go run -race Picocrypt.go` now yields no issues</strike></li>
<li>✓ Fix a race condition</li>
<li>✓ Fix invalid pointer crash when decrypting files >256GB</li>
<li>✓ UI improvements and tweaks</li>
<li>✓ Fix crash on Windows when saving to the root directory of a drive</li>
@ -63,7 +63,6 @@
# v1.23 (Released 03/19/2022)
<ul>
<li><strike>Remove EXIF data from keyfiles</strike> (there is no native or "official" EXIF stripper, and existing implementations are either not written in Go, or experimental)</li>
<li>✓ Removed the checksum generator to get back on track with original Picocrypt ideology</li>
<li>✓ Cleaned up and optimized code</li>
<li>✓ Compiled with MinGW GCC11 instead of TDM-GCC, Go 1.18 instead of Go 1.17</li>
@ -72,8 +71,6 @@
# v1.22 (Released 12/22/2021)
<ul>
<li><strike>Customizable Argon2 parameters</strike> (the default parameters are already overkill, and paranoid mode is even more. There really is no practical need for customizable Argon2 because the current default parameters are high enough that any higher parameters won't offer any added security)</li>
<li><strike>Fix keyfile order bug</strike> (redundant, so there actually was no bug)</li>
<li>✓ Remove fast mode, as a change for the normal mode will make fast mode obselete</li>
<li>✓ For normal mode, change HMAC-SHA3 to a keyed Blake2b</li>
</ul>
@ -91,7 +88,7 @@
<li>✓ Fix keyfile modal typo</li>
<li>✓ Fix minor keyfile bug</li>
<li>✓ Improve shredding window layout</li>
<li>✓ Fork all dependencies and recursive dependencies (excluding golang.org/x/*) into "offline" repos for hardening and better stability</li>
<li>✓ Fork all dependencies and recursive dependencies into "offline" repos for hardening and better stability</li>
<li>✓ Fix UI scaling issues</li>
<li>✓ Fix high DPI layout issues</li>
<li>✓ Optimize zip compressor</li>
@ -112,7 +109,6 @@
</ul>
# v1.17 (Released 09/04/2021)
<strong>Note: v1.17 will be incompatible with 1.16 (and therefore 1.15 and 1.14).</strong>
<ul>
<li>✓ (abandoned due to UI issues with ASCII codes >128) Extended ASCII set in password generator</li>
<li>✓ Tooltips for all advanced options</li>
@ -127,10 +123,10 @@
<li>✓ Prevent duplicate keyfile</li>
<li>✓ Add a select keyfile button</li>
<li>✓ Make sure only one of "Fast mode" and "Paranoid mode" can be enabled</li>
<li>✓ (abandoned because this could cause issues with different language characters) Filter invalid charaters and emojis out of "Save as" text entry</li>
<li>✓ Fix bug where metadata says "read-only", but the textbox is modifiable</li>
<li>✓ Add option to delete encrypted files after decryption</li>
</ul>
<strong>Note: v1.17 will be incompatible with all previous releases!</strong>
# v1.16 (Released 08/11/2021)
<ul>
@ -152,7 +148,6 @@
</ul>
# v1.14 (Released 08/07/2021)
<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>
<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 the latter being stateful</li>
@ -166,20 +161,20 @@
<li>✓ Reed-Solomon checkbox is now enabled and Reed-Solomon works</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>✓ Fixed Windows zip extract error notice that doesn't appear in 7-Zip (edit: it was a backslash and forwardslash issue)</li>
<li>✓ Fixed Windows zip extract error notice that doesn't appear in 7-Zip (edit: it was a backslash issue)</li>
<li>✓ Optional shred temporary files checkbox</li>
<li>✓ Remove BLAKE3 from the checksum generator tab, as it has no practical use and requires a non-standard library</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>✓ Reduce padding of metadataLength from 10 to 5 (you probably won't type more than 99999 metadata characters)</li>
<li>✓ Use regex to check if an input file is a valid Picocrypt volume or not (during decryption)</li>
<li>✓ Use regex to check if an input file is a valid Picocrypt volume or not during decryption</li>
<li>✓ Improved user flow as well as fix UI bugs</li>
<li>✓ Code optimizations</li>
<li>✓ Many bug fixes/stability improvments</li>
</ul>
<strong>Note: v1.14 will be incompatible with all previous releases!</strong>
# v1.13 (Released 5/29/2021)
<strong>Note: v1.13 will be INCOMPATIBLE with all previous releases! <s>This will likely be the last change in the header format, meaning that all future releases _should_ be compatible with v1.13 and on.</s></strong>
<ul>
<li>✓ Picocrypt has been ported from Python to Go, thus completely rewritten</li>
<li>✓ Added fast mode, which can achieve ~250MB/s</li>
@ -187,9 +182,12 @@
<li>✓ Automatically checks for newer versions</li>
<li>✓ Added file chunking support</li>
</ul>
<strong>Note: v1.13 will be incompatible with all previous releases!</strong>
# v1.12.1 (Released 04/11/2021)
There was a major bug in v1.12 that caused the "Secure wipe" feature to show "Unknown error" when done. This wasn't anything serious security-wise and v1.12.1 has the fix for this bug. Also, a bug that causes "Secure wipe" to hang has been fixed.
<ul>
<li>✓ Fixed a bug that caused "Secure wipe" feature to show "Unknown error" when done</li>
</ul>
# v1.12 (Released 04/07/2021)
<ul>
@ -204,14 +202,14 @@ There was a major bug in v1.12 that caused the "Secure wipe" feature to show "Un
<li>✓ Switch from SHA3 to BLAKE3 for corruption check</li>
<li>✓ Better user flow</li>
</ul>
<strong>Note: v1.12 will be INCOMPATIBLE with all previous releases!</strong>
<strong>Note: v1.12 will be incompatible with all previous releases!</strong>
# v1.11 (Released 03/23/2021)
<ul>
<li>✓ Much more secure wipe via <code>sdelete64</code> for Windows, <code>shred</code> for Linux, and <code>rm -P</code> for MacOS</li>
<li>✓ Much more beautiful UI for MacOS</li>
<li>✓ Much more beautiful UI for macOS</li>
<li>✓ Robust secure wipe support for drag and dropped files/folders</li>
<li>✓ Only open input files in read mode, since write mode is unnecessary</li>
<li>✓ Clean up source code, add better comments</li>
<li><strong>New: </strong>Drag and drop support (multiple files, a folder, a file and a folder, etc.)</li>
<li>✓ Drag and drop support (multiple files, a folder, a file and a folder, etc.)</li>
</ul>