All changes to the software that can be noticed from the users' perspective should have an entry in this file. Except very minor things that will not affect functionality.
The format is based on Keep a Changelog.
Entries should have the imperative form, just like commit messages. Start each entry with words like add, fix, increase, force etc.. Not added, fixed, increased, forced etc.
Line wrap the file at 100 chars. That is over here -> |
- Added: for new features.
- Changed: for changes in existing functionality.
- Deprecated: for soon-to-be removed features.
- Removed: for now removed features.
- Fixed: for any bug fixes.
- Security: in case of vulnerabilities.
- Change from implementing NIST round 3 specification of Classic McEliece to NIST round 4
- Move non kem-API interface related tests out of kem module
- Exclude testdata folder & files from published crates in order reduce crate size
- Add a separate CHANGELOG.md file to the project
- Added tests for the Ciphertext EncappedKeySize, such that
CryptoCiphertextBytesTypenumalways matches the length ofCRYPTO_CIPHERTEXTBYTES
- Improve & fix unit tests
- fix casting to same type clippy warnings
- Fix README documentation
- Implement zeroize functionality on structs holding sensitive key material
- Implement RustCrypto's
kemAPI - Add
allocfeature that exposes convenient helper functions to automatically allocate large key material on the heap
- Rewrite a lot of the public API
- Make SHAKE implementation infallible
- Forbid unsafe code
- Fix Copy and paste mistakes in documentation
- public release (no April fools though). Implements NIST round 3 version of Classic McEliece.