Enable OpenSSL compiling in Linux#2
Conversation
|
Thank you @aberenguel! @arisjr I wonder if APFS encryption support works on your environment without this, does it? |
|
The patch I made should add HAVE_LIBOPENSSL if it has the dev libs test passed. I made a pull on tsk also https://github.com/sleuthkit/sleuthkit/pull/2781/files that shows the change, but this PR was closed after because I needed to remove the sleuthkit fork from my account. The patch was tested by the issue creator and others and worked at the time, but I didn't test on all environments. The patch I made was to be used with openssl 1.1x, the lib version that was tested when APFS support was made by the author (that has not being changed since then). I must say that using openssl 3 is somehow not tested. On the ipeddocker, even using Ubuntu 22.04 as a base system, we made a "hack" to use Ubuntu 20.04 openssl 1.1 dev libs for compiling with the APFS support. |
|
I must allocate some time to look it closely anyway. I'll take a look at the end of the day. |
|
I'm getting this bug again (ubuntu 26.04). The solution is to run the command My suggestion is to remove this file from the repository in order to force the user to run |
Related to sleuthkit#2862 (comment)
In order to compile APFS decryption code, the flag
HAVE_LIBOPENSSLmust be defined. However, even after running./configureand the output shows the output bellow and the flag is not defined.After run
autoheadercommand, the flagHAVE_LIBOPENSSLcame back totsk_config.h.in. So the APFS decryption code was compiled.PS: Using Ubuntu 22.04.
Btw, Ubuntu 22.04 has OpenSSL 3.0. So in order to avoid deprecated errors in compilation, the configure must be run with: