Switching from openssl-1 to openssl-3?

How should I do this. I see that both are installed. But when I ask for version, I get this:

mprowe@Gzunder:~> openssl version -a
OpenSSL 1.1.1l 24 Aug 2021 SUSE release 150500.17.15.1

platform: linux-x86_64
options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O3 -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -fstack-protec
tor-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g -fpatchable-function-entry=16,14 -fdump-ipa
-clones -Wa,--noexecstack -fno-common -Wall -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_
SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -
DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DZLIB -DNDEBUG -D_FORTIF
Y_SOURCE=2 -DTERMIO -DPURIFY -D_GNU_SOURCE -DSUSE_OPENSSL_RELEASE=150500.17.15.1 -DOPENSSL_NO_BUF_FREELISTS -DSYSTEM_CIPHERS_FI
LE="/etc/crypto-policies/back-ends/openssl.config"
OPENSSLDIR: "/etc/ssl"
ENGINESDIR: "/usr/lib64/engines-1.1"
Seeding source: getrandom-syscall
mprowe@Gzunder:~>

I need to switch to openssl-3 to run an AppImage.

Regards, Martin

Operating System: openSUSE Leap 15.5
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.14.21-150500.55.31-default (64-bit)
Graphics Platform: X11
Processors: 32 × 13th Gen Intel® Core™ i9-13900
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: ASUS
1 Like
bor@leap15:~> openssl-3 version -a
OpenSSL 3.0.8 7 Feb 2023 (Library: OpenSSL 3.0.8 7 Feb 2023)

platform: linux-x86_64
options:  bn(64,64)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O3 -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g -Wa,--noexecstack -fno-common -Wall -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DZLIB -DNDEBUG -D_FORTIFY_SOURCE=2 -DTERMIO -DPURIFY -D_GNU_SOURCE -DOPENSSL_NO_BUF_FREELISTS -DSYSTEM_CIPHERS_FILE="/etc/crypto-policies/back-ends/openssl.config"
OPENSSLDIR: "/etc/ssl"
ENGINESDIR: "/usr/lib64/engines-3"
MODULESDIR: "/usr/lib64/ossl-modules"
Seeding source: getrandom-syscall
CPUINFO: OPENSSL_ia32cap=0x80202001479bffff:0x0
bor@leap15:~> 

Yes. You can do that at the command line.
But (I suspect) the call within the AppImage is just “openssl”.
I was hopping for a technique like that used with packages like python or java where you can a direct base name (python, java or in my case) openssl to the required version.

To part answer my own question. Following additional research, I think a solution may be:
alternatives and update-alternatives
There is also a management tool in the Yast Control Center. My problem now is how to use the tool to safely switch from the currently defined openssl = openssl-1 to openssl = openssl-3.
Reading the very limited Help, it only covers editing existing entries and not creating new ones.

Can anyone offer any help?

Regards, M.