bsdtar.exe 3.7.0 does not work without libcrypto-1_1-x64.dll

[hemnstill]

Windows 10 Home 22H2 19045.3208

Error: The code execution cannot proceed because libcrypto-1_1-x64.dll was not found. Reinstalling the program may fix this problem.

It looks like the behavior changed after this commit: https://github.com/libarchive/libarchive/commit/d3d16ec25d695b186c25f31b6bab1c4401122a3e

SET(CMAKE_REQUIRED_LIBRARIES ${OPENSSL_CRYPTO_LIBRARY})

I want to build static version of bsdtar that working without any additional dll's

[lelik107]

I've got the same behavior I've never seen before. Why do we need external cryptographic library in TAR that's not even included in release files?

[evelikov]

A while ago we've spotted that our use of the wincrypto code is broken.

The mentioned commit fixes a genuine bug and it enforces what was the default for years - use openssl.

Although I can understand the annoyance, that's more of a Windows problem than libarchive's. @mmatuska sounds like we'll need to keep the wincrypt code forever? Unless you're a fan of shipping a release with openssl statically linked in.

The references issues are duplicates. Can anyone @kientzle (?) do the honours and close them ;-)

[9001]

Seems the latest release binaries still fail to start;

The dll from python-3.10.11-embed-amd64.zip, once renamed, seems to work -- is this a good choice?

or rather, what is the recommended place to obtain this dll from? How can I know that I am using a compatible version?

[lelik107]

Yes you can use it. The latest Python build with OpenSSL 1.1.1u was: https://www.python.org/ftp/python/3.11.4/python-3.11.4-embed-amd64.zip and they switched to OpenSSL 3 after it.

[3052]

this is really annoying - I will just use another tool I guess

[kientzle]

I think there are three alternatives for us here:

• Support building without crypto support. This would have to disable all support for encrypted archives, of course, but is similar to what we already do when we cannot locate a functioning LZMA or ZStd library, for instance.
• Default to using a crypto library that is built into Windows.
• Build a proper installer for bsdtar that includes redistributable libraries.

If anyone would like to try implementing one of these, please let us know.

[kientzle]

BTW @3052 if you are looking for a very basic tar program with no external dependencies, you might consider this one: https://github.com/libarchive/libarchive/blob/master/contrib/untar.c

[9001]

As a 4th alternative, would it be possible to statically link libcrypto into the exe? Or perhaps that is problematic somehow? License-wise it should be alright, and it looks like it should be fine technically as well -- but I have no experience with building for windows, so I could be way off.

[lelik107]

For now bsdtar relies on libcypto-1_1-x64.dll that is not updated publicly anymore, there's no need to recompile it every time. Why not just to build this dll once and place it in a "bin" folder with bsdtar.exe, IDK. The latest public sources: https://github.com/openssl/openssl/releases/tag/OpenSSL_1_1_1w