<commit_before>CryptoJPM
=========

public fork of Crypto++ v5.6.2 to add algorithms

algorithms include:
-Skein
-Threefish
-Fortuna(unfinished)
-BLAKE2s/b/sp/bp (unfinished/bugged?)
-scrypt (unfinished/bugged?)

planned algorithms:
-post-quantum public key cryptography (mceliece?)
-PHC winner(s)
-Argon PBKDF as it is optimized for desktops/servers (man appliance of Crypto++ / CryptoJPM)

production use is NOT recommended

You can use some parts of this fork for production use.
If you are on a little-endian machine (x86, x64, ARM) you can use everything but scrypt, BLAKE2s/sp and if on X86 you can't use BLAKE2b/bp.
Usage of Fortuna is strongly not recommended, as this is unfinished yet.
Everything else SHOULD be fine, but is not guaranteed to be so.

SSE code of BLAKE2s, BLAKE2sp, scrypt and x86-BLAKE2b and X86-BLAKE2bp is broken and produces wrong results (as far as my tests go, test code is included)

What needs to be done:
-If you wish you can review every piece of code
-Fortuna random event collecting code is currently wip
-one can test/correct the above mentioned (broken) SSE codes
-one can contribute planned algorithms(orient at Crypto++/CryptoJPM's style of formatting and class structures), note that the file header should be set and the code will be placed in the public domain<commit_msg>updated readme formatting<commit_after>CryptoJPM
=========

public fork of Crypto++ v5.6.2 to add algorithms

algorithms include:
- Skein
- Threefish
- Fortuna(unfinished)
- BLAKE2s/b/sp/bp (unfinished/bugged?)
- scrypt (unfinished/bugged?)

planned algorithms:
- post-quantum public key cryptography (mceliece?)
- PHC winner(s)
~~- Argon PBKDF as it is optimized for desktops/servers (man appliance of Crypto++ / CryptoJPM)~~

production use is NOT recommended

You can use some parts of this fork for production use.
If you are on a little-endian machine (x86, x64, ARM) you can use everything but scrypt, BLAKE2s/sp and if on X86 you can't use BLAKE2b/bp.
Usage of Fortuna is strongly not recommended, as this is unfinished yet.
Everything else SHOULD be fine, but is not guaranteed to be so.

SSE code of BLAKE2s, BLAKE2sp, scrypt and x86-BLAKE2b and X86-BLAKE2bp is broken and produces wrong results (as far as my tests go, test code is included)

What needs to be done:
- If you wish you can review every piece of code
- Fortuna random event collecting code is currently wip
- one can test/correct the above mentioned (broken) SSE codes
- one can contribute planned algorithms(orient at Crypto++/CryptoJPM's style of formatting and class structures), note that the file header should be set and the code will be placed in the public domain
{'fraction_non_alphanumeric': 0.067618332081142, 'fraction_numerical': 0.015026296018031555, 'mean_word_length': 4.490721649484536, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1931944', 'n_tokens_mistral': 831, 'n_tokens_neox': 802, 'n_words': 389}