It uses `electron-builder`, which has rpm support. I don't think it would be that difficult to add in a pull request, might do it myself later. (I use Fedora, with SELinux and Wayland and all that good stuff)

Here's something to work off of: https://whispersystems.discoursehosting.net/t/signal-desktop...

I think you underestimate the number of people whose first post-installation task is setenforce 0

I know no Linux admin (good or not) that does that. It's 2017.

There are also people that run as root...

> SELinux means you are getting the people who value security

Proper, very strict sandboxes implemented with seccomp & friends are much more secure. You simply block the large majority of system calls.

Surprisingly, they are often easier to set up.

Can you recommend any distros that use it extensively, or is it too early?

Ideally upstreams, rather than distributions, should sandbox their own projects.

However, Debian is shipping a number of hardened systemd unit files.

To see some examples on how the sandboxing is being set up you can grep for SystemCallFilter, CapabilityBoundingSet, ProtectSystem, ProtectHome in /lib/systemd/system/*.service

Fedora doesn't support APT right? It needs to be packaged separately? So it's a whole bunch of work for a small user base.

It's a different user base. Give us a github repo and we can build it ourself. Let me see if I can find one.

Edit: https://github.com/WhisperSystems/Signal-Desktop

Moxie strictly disagrees with that, and has previously tried to shut down every third-party build of Signal, even in repos for distros or F-Droid.

He only wants users to get Signal builds from himself, and no one else.

Oh come on kuschku, stop it with the deliberate misinformation about Signal! You bring nonsense like this up in just about every thread on Signal and it's becoming harder and harder to assume that you operate in good faith.

Moxie is most decidedly not against building the code yourself. He doesn't want anyone distributing forks or other clients using the official servers because a) that creates a giant hassle when updating the server and suddenly someone's fork doesn't work anymore and people will blame Signal, and b) if the client doesn't do what they want it to, people will blame Signal even though it's a third-party bug because it's got Signal in the name.

How the fuck is this misinformation?

Moxie has publicly stated that he is against anyone publishing a third-party build of Signal.

He has openly and loudly ranted against F-Droid. Of course he's not against users building it for themselves, but he's publicly stated he won't allow F-Droid, or distributions, or anyone else, to build and publish the client, under the name Signal, so that it can connect to his servers.

Read the Signal-Android issues https://github.com/WhisperSystems/Signal-Android/issues/53 https://github.com/WhisperSystems/Signal-Android/issues/127 https://github.com/WhisperSystems/Signal-Android/issues/281 and https://github.com/WhisperSystems/Signal-Android/issues/6292, where moxie publicly states that he will not accept or allow any public distribution of third-party builds of Signal to connect to his servers.

He actually directly reached out to F-Droid, and demanded they take it down: https://web.archive.org/web/20160410152543/https://f-droid.o...

So, how the fuck is what I'm saying misleading?

EDIT: Oh, right, some of the linked issues were purged by him later on. Here's an archive.org link: https://web.archive.org/web/20160410153027/https://github.co...

EDIT2: The real question is why you continue to lie to defend Signal.

noja said: "Give us a github repo and we can build it ourself" and I pointed out that moxie never opposed it when people build the code themselves. I'm not denying that he doesn't like it when people distribute their own builds (F-Droid) or forks (LibreSignal), and I'm not a fan of that policy either. But I understand why he's acting this way. If you read the issues you so kindly linked, he explains his reasons, and they are valid points to make even if I don't like their consequences. It's a pity that as a result, Signal is controlled by a small group of people in Silicon Valley, just like any other software product these days. I would like to have a good native desktop client just as much as you. But that's not a reason to misrepresent his position, or to inject it into only tangentially related discussions.

I’m interpreting it in the way that noja is writing it from the perspective of distributions. As in, just link us a repo, and we (Fedora) can include it. That interpretation might be wrong, and I might have misinterpreted it because I’ve been working with distro maintainers on getting some of my software into distributions recently.

But with that interpretation (and the context around that, where users asked about including it in distros), my arguments are certainly relevant.

> If you read the issues you so kindly linked, he explains his reasons, and they are valid points to make even if I don't like their consequences.

His points are basically irrelevant if compared to the risks that the centralization causes.

Users of distributions have to trust their distro anyway, for many other packages (including the kernel build) already, trusting them for Signal, too, actually reduces the number of parties you have to trust.

EDIT3: Almost forgot, also you should read this comment where Moxie addressed LibreSignal: https://github.com/LibreSignal/LibreSignal/issues/37#issueco...

Then he shouldn't release the code.

I'll simply quote moxie here.

On the topic of LibreSignal, a fork with the only change being that it supports notifications without relying on proprietary libraries:

> I'm not OK with LibreSignal using our servers, and I'm not OK with LibreSignal using the name "Signal." You're free to use our source code for whatever you would like under the terms of the license, but you're not entitled to use our name or the service that we run.

https://github.com/LibreSignal/LibreSignal/issues/37#issueco...

Basically, he argues that no one but him has the right to build a client that connects to his servers.

Disclaimer: I personally am critical of Moxie's demands that he fully controls all released client builds, servers, and his use of analytics.

Small user base? I think not...