John P. Lucas
John P. Lucas
Per https://github.com/nasa/CryptoLib/pull/232#discussion_r1539437911
Should a single key only map to a specific security association? Document this per the standard as well as how it's currently implemented.
* Should configurations be a part of the "Monitoring and Control" or separate? * Cody suggested in https://github.com/nasa/CryptoLib/pull/166#pullrequestreview-1482136077 breaking apart the existing Crypto_Config_CryptoLib function into two calls: Crypto_Config_Interfaces and Crypto_Config_Behavior....
Should testing be performed in cycles? * Setup a specific configuration (managed parameters and SA parameters) then run all the tests in that configuration? Rinse and repeat? Can the PICs...
What should be the default SA configuration for use? 0, TC, clear 1, TC, authenticated encryption 2, TC, encryption only 3,TC, authentication only … 8, TM, clear 9, TM, authenticated...