Describe the bug
Well, one could say, the latest appimage is getting outdated in terms of dependencies. E.g. It seems to be dependent on OpenSSL1.1 which is deprecated, the pin returns "false" with only OpenSSL3 installed.
To Reproduce
Steps to reproduce the behavior:
Replace OpenSSL1.1 with OpenSSL3
Start Criptext (appimage)
Enter pin
See error "false pin"
Expected behavior
The pin, of course, is correct, but is not accepted because criptext appimage seems to depend on the now deprecated OpenSSL1.1
Screenshots (Optional)
Device and System information (please complete the following information):
Thinkpad
Linux, kernel v6.1, glibc 2.38, openssl3 (and 1.1, only because of criptext appimage)
App Version: 0.31
Additional information
I found some information about openssl3 not being able to decrypt openssl1.1 generated stuff, but that was way back when and has een fixed. Also, I tried creating a new key with only openssl3 installed, so the key would not be generated by openssl1.1 and thus make sure it's not openssl3 not being able to decrypt a key generated using openssl1.1, but criptext isn't able to create a key (from login + password) with only openssl3 installed. As soon as openssl1.1 ist installed, all is fine.
With this issue in mind I wanted to build the appimage from source against the current versions of the respective dependencies. But unfortunately, I couldn't find any description on how to do that.
Describe the bug Well, one could say, the latest appimage is getting outdated in terms of dependencies. E.g. It seems to be dependent on OpenSSL1.1 which is deprecated, the pin returns "false" with only OpenSSL3 installed.
To Reproduce Steps to reproduce the behavior:
Expected behavior The pin, of course, is correct, but is not accepted because criptext appimage seems to depend on the now deprecated OpenSSL1.1
Screenshots (Optional)
Device and System information (please complete the following information):
Additional information I found some information about openssl3 not being able to decrypt openssl1.1 generated stuff, but that was way back when and has een fixed. Also, I tried creating a new key with only openssl3 installed, so the key would not be generated by openssl1.1 and thus make sure it's not openssl3 not being able to decrypt a key generated using openssl1.1, but criptext isn't able to create a key (from login + password) with only openssl3 installed. As soon as openssl1.1 ist installed, all is fine.
With this issue in mind I wanted to build the appimage from source against the current versions of the respective dependencies. But unfortunately, I couldn't find any description on how to do that.