Signal only provides a script for .deb based distros on their official website. The flatpak is currently not ideal because it stores encryption keys in plaintext.
The provided link suggests an automated installation in a Ubuntu Distrobox including automated updates. Useful for every distro that does not natively support .deb packages.
FYI, OpenSuse maintains .rpm builds of the signal app in their repos, specifically targeted at OpenSuse Leap and Fedora. They work great for me.
i mean its great if it works well, but kinda funny we need to run a full distro in a container to run a browser to run an IM program
They’ve recently released a beta of an AppImage https://community.signalusers.org/t/beta-test-the-signal-desktop-linux-appimage/73330
This is great, but sadly appimages don’t work on immutable desktops. But it’s very positive that they are providing that.
Appimages definitely work on Bazzite
I have used sivlerblue, kinoite and bazite. Each one of them could run appimages. What are you using?
I have no clue why they’re not just adopting the existing flatpak that a majority of Linux users use
Flatpak signal can integrate with kwallet and gnome keyring, so unless I’m missing something, you’re wrong.
Yeah, I have been using it like that for a while. It is just a single environment variable.
Not by default, IIRC, and the integration is still marked as experimental - so just what the readme is saying.
it literally prompts you to enable it and is just one command. I get Linux can be hard, but setting up an entire distrobox just to avoid entering the single command.
Also the only reason it’s experimental is because you have to enter that command manually, not because it’s any less safe.
I mean, I use the Flatpak, but I have also run into breakage concerning the experimental support, resulting in Signal Desktop no longer being able to start, and me having to track down a GitHub issue with a workaround. I can imagine wanting to run the Distrobox just so you’re closer to a system that the upstream developers actually test with - not so much to avoid running a single command, but to lower risk of breakage.
That’s interesting, Ig it really can break.
Yeah unfortunately i can’t quite recall the context, but I think they were attempting to make encrypted storage the default, but then that broke on existing databases or something? It was a pain at least, I know that much 😅
(Although would be less of a pain nowadays, now that Signal has proper sync to restore my history.)
Sorry where does the .deb version store the encryption keys if not in plaintext?
I think in kwallet or another keyring depending on your DE or setup.
