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...
This addresses #240 and #239 Addition of Custom Module path variables and cmake options Addition of Custom Crypto Module, as well as pathing variables in Cmake.
Per https://github.com/nasa/CryptoLib/pull/232#discussion_r1539437911
Remove the char* pointers that are associated with ak_ref and ek_ref within the SA stuctures. This will aid in allowing fread/write to more easily save files. The current default value...
In order to support the integration of a hardware crypto unit, a custom interface stub should be created for the crypto module
Path variables for the custom module source files should be added to the cryptolib CMake files. If the variable is not set, then a default path can be used. For...
Refactor sadb_routine_mariadb_template.c - parse_sa_from_mysql_query #196
Refactor cryptography_interface_kmc_crypto_service_template.c - cryptography_aead_encrypt - cryptography_encrypt - cryptography_authenticate - cryptography_aead_decrypt #196
Refactor base64.c for kmc_crypto_service. base64Decode function. #196
Update the wiki to be more understandable. Clarify anything that was confusing during initial install
CCSDS 355.1-B-1 indicates that the length field of EP PDUs should be the length of the PDU data field in **bits**: > **5.3.2.3.1** The Extended Procedures Data Field Length shall...
