CryptoLib
CryptoLib copied to clipboard
nasa
Provide a software-only solution using the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between a spacecraft running the core Flight System (cFS) an...
In crypto_config.h line 153 (collab_main branch): `#define SG_SEC_MON_CTRL 0b11` should be: `#define SG_SEC_MON_CTRL 0b10`
This test is commented out in the latest `dev` branch and ideally is run.
Wish to improve logic in scenarios such as follows in updated version of crypto_tm.c: ``` if((*(sa_ptr->acs) == CRYPTO_MAC_CMAC_AES256 || *(sa_ptr->acs) == CRYPTO_MAC_HMAC_SHA256 || *(sa_ptr->acs) == CRYPTO_MAC_HMAC_SHA512) && sa_ptr->iv_len > 0...
Add support for a custom crypto module, in order for the SMaCS team to interface cryptolib with the Matchbox crypto IP Known updates required: - add function definition `CryptographyInterface get_cryptography_interface_custom(void);`...
The `GvcidManagedParameters_t` struct has a `has_ocf` field [defined here](https://github.com/nasa/CryptoLib/blob/main/include/crypto_config_structs.h#L233), but there isn't an argument to the [Crypto_Config_Add_Gvcid_Managed_Parameter()](https://github.com/nasa/CryptoLib/blob/main/src/core/crypto_config.c#L474) function or the [crypto_config_add_gvcid_managed_parameter_recursion()](https://github.com/nasa/CryptoLib/blob/main/src/core/crypto_config.c#L592) function in `crypto_config.c`
Allows for AES-GCM-SIV Enc/Dec. Examples are supplied via unit tests in `ut_aes_gcm_siv.c`.
Python helper scripts: - Generate baseline databases for keys / etc. - Confirm same databases for flight and ground sides - Maybe Truth data generation?
Need to add versioning to docker container similar to what was done in NOS3 so that feature development can occur outside of general use without confusion.
Look to get cyclomatic complexity and MC/DC coverage reported as part of the CI process.