Criptext / Criptext/Criptext-Email-React-Client

How to build appimage from source (against current versions of dependencies)?

Open
#1,537 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
75
Forks
23
PR merge metrics
No merged PRs in 30d

Description

**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:
1. Replace OpenSSL1.1 with OpenSSL3
2. Start Criptext (appimage)
3. Enter pin
4. 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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.