Donovan Ice
Donovan Ice
https://public.ccsds.org/Pubs/355x1b1.pdf (Page 3-1)
According to @dccutrig, all Key Management unit tests are passing with no changes to the code. Can now resume work on this.
Put a halt on this due to rapidly increasing cyclomatic complexity. If you replace the early returns with a status message that gets returned at the end, you must add...
[SDLS-EP](https://public.ccsds.org/Pubs/355x1b1.pdf) (Page 4-2)
WolfSSL only has support for AES_SIV, not AES_GCM_SIV. [(ref)](https://crypto.stackexchange.com/questions/87895/aes-gcm-siv-implementation) [(ref)](https://www.wolfssl.com/documentation/manuals/wolfssl/group__AES.html#function-wc_aessivencrypt)
[RFC 8452 - AES_GCM_SIV](https://datatracker.ietf.org/doc/rfc8452/?include_text=1) [OpenSSL Test Vectors](https://github.com/openssl/openssl/blob/a2b1ab6100d5f0fb50b61d241471eea087415632/test/recipes/30-test_evp_data/evpciph_aes_gcm_siv.txt)
Default format code is checked against: https://llvm.org/docs/CodingStandards.html
I don't see the need for the `crypto_increment()` to be in a for loop, but the function call itself looks good. For the second increment, you maybe able to call...
Running ~half of the tests. Can't use AAD or compare encrypted PT to Ciphertext, but could expand code coverage
Scrapping this. This was more of a libgcrypt verification than cryptolib.