Cryptographically Signed Releases

[maltfield]

Description

Currently it is not possible to verify the authenticity or cryptographic integrity of the downoads from your website or github.com because the releases are not cryptographically signed.

This makes it hard for epicyon users to safely obtain the epicyon software, and it introduces them (and potentially their instance's users' data) to watering hole attacks.

Steps to Reproduce

1. Go to the this repo
2. Look for releases and information about verifying signatures
3. See there's a website
4. Go to the website https://libreserver.org/epicyon/
5. Look for information about verifying signatures
6. ???
7. Open Ticket

Expected behavior: [What you expected to happen]

A few things are expected:

1. I should be able to download the epicyon PGP key out-of-band from popular third-party keyservers (eg https://keys.openpgp.org/)
2. I should be able to download a cryptographic signature of the release (or, better, the releases' digest file, such as a SHA256SUMS.asc file) along with the release itself
3. The downloads page itself should include a link to the documentation page that describes how to do the above two steps

Actual behavior: [What actually happened]

There's just literally no information on verifying downloads, and it appears that it is not possible to do so.

[maltfield]

Related: the latest release page links to a 404'd release :(

• https://libreserver.org/epicyon/v1_5_0.html
• https://libreserver.org/epicyon/epicyon.tar.gz