On Wed, 23 Nov 2022 14:08:58 +0100 Sylvain Rochet <grada...@gradator.net> wrote:
Attached patch is a better approach to fix that by loading providers in main instead of crypto module. That way it also works for legacy VTun crypto module (VTun <= 2.6) if there are any users left and is future proof for auth module.
Thanks Sylvain, your patch made my day! Ever since updating to bookworm a few weeks ago I had segfaults instead of tunnel connections from vtun 3.0.4-2+b1, amd64 architecture. Adding 13-libssl-use-legacy-provider.patch solved that for my bookworm-based server and client, and I can finally use vtun it again - to remotely maintain a bullseye-based laptop of a relative (sigh), and as 2nd VPN into our company's HQ. Best regards, Christoph
