John P. Lucas
John P. Lucas
Take a look and use "const" where possible
Should we stick with double pointers? Maybe also provide a single pointer option?
* [20240123_CryptoLib_Requirements_Notes.pdf](https://github.com/nasa/CryptoLib/files/14188393/20240123_CryptoLib_Requirements_Notes.pdf) * [20240206_CryptoLib_PICS.pdf](https://github.com/nasa/CryptoLib/files/14188396/20240206_CryptoLib_PICS.pdf)
``` # CryptoLib Requirements This short document is to be used to capture the CryptoLib requirements. ## Level 1 * CryptoLib shall enable compliance with NASA-STD-1006A for both ground and...
Merged into `dev`
Looks like maybe our version of libgcrypt may not have the functionality for it to manage the IV for us just yet: https://dev.gnupg.org/T4873 Need to do some more research.
Merged into `dev`
Not actually CryptoLib but the required steps in the Dockerfile, specifically the gpgerror and libgcrypt steps. In the interim I moved back a commit to `dev` and created a branch...
``` 35.60 mv -f .deps/t-secmem.Tpo .deps/t-secmem.Po 35.60 /bin/bash ../libtool --tag=CC --mode=link gcc -I/usr/local/include -g -O2 -fvisibility=hidden -fno-delete-null-pointer-checks -Wall -no-install -o t-secmem t-secmem.o ../src/libgcrypt.la ../compat/libcompat.la 35.63 libtool: link: gcc -I/usr/local/include -g...
Pushed up a `dev` image, but still having an error on internal: ``` [ 35%] Linking C executable standalone /usr/bin/ld: /usr/local/lib/libgcrypt.so: undefined reference to `gpgrt_logv_domain@GPG_ERROR_1.0' /usr/bin/ld: /usr/local/lib/libgcrypt.so: undefined reference to...