JaehaerysNL/Picocrypt
1
0
Fork 0
mirror of https://github.com/HACKERALERT/Picocrypt.git synced 2024-12-29 10:53:03 +00:00
Code Releases Activity

Fix typo

Browse source
This commit is contained in:
Evan Su 2021-11-19 23:52:13 -05:00 committed by GitHub
parent 17e23382b9
commit 9b12e8cce1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
Internals.md
View file

@ -3,8 +3,8 @@ If you're wondering about how Picocrypt handles cryptography, you've come to the
# Core Cryptography # Core Cryptography
Picocrypt uses the following cryptographic primitives: Picocrypt uses the following cryptographic primitives:
- XChaCha20 (cascaded with Serpent-CTR for paranoid mode) - XChaCha20 (cascaded with Serpent in CTR mode for paranoid mode)
- HMAC-SHA3 for normal annd paranoid mode, keyed-BLAKE2b for fast mode (256-bit key, 512-bit digest) - HMAC-SHA3 for normal and paranoid mode, keyed-BLAKE2b for fast mode (256-bit key, 512-bit digest)
- HKDF-SHA3-256 for deriving a subkey used with the MAC above, as well as a key for Serpent - HKDF-SHA3-256 for deriving a subkey used with the MAC above, as well as a key for Serpent
- Argon2id: - Argon2id:
- Fast mode: 4 passes, 128 MiB memory, 4 threads - Fast mode: 4 passes, 128 MiB memory, 4 threads
@ -18,4 +18,4 @@ Picocrypt allows the use of keyfiles as an additional (or only) form of authenti
If "Require correct order" is not checked, Picocrypt will take the SHA3 hash of each file individually, and XORs the hashes together. Finally, the result is XORed to the master key. Because the XOR operation is both commutative and associative, the order in which the keyfiles hashes are XORed to each other doesn't matter -- the end result is the same. If "Require correct order" is not checked, Picocrypt will take the SHA3 hash of each file individually, and XORs the hashes together. Finally, the result is XORed to the master key. Because the XOR operation is both commutative and associative, the order in which the keyfiles hashes are XORed to each other doesn't matter -- the end result is the same.
If "Require correct order" is checked, Picocrypt will combine (concatenate) the files together in the order they were dropped into the window, and take the SHA3 hash of combined keyfiles. If the order is not correct, the keyfiles, when appended to each other, will result in a different file, and therefore a different hash. Thus, the correct order of keyfiles has been enforced. If "Require correct order" is checked, Picocrypt will combine (concatenate) the files together in the order they were dropped into the window, and take the SHA3 hash of the combined keyfiles. If the order is not correct, the keyfiles, when appended to each other, will result in a different file, and therefore a different hash. Thus, the correct order of keyfiles is required to successfully decrypt the volume.