The user requests that releases be cryptographically signed to verify the authenticity of the downloads.
### Description Currently it is not possible to verify the authenticity of the downloads from sourceforge.net, github.com, or phplist.org because the releases are not cryptographically signed. This makes it hard for phpList users to safely obtain the phpList software, and it introduces them (and potentially their customer's data) to watering hole attacks. ### Steps to Reproduce 1. Go to the https://www.phplist.org/download-phplist page 2. Go to Sourceforge download page https://sourceforge.net/projects/phplist/files/phplist/ 3. Click the version directory 4. Click download 5. ??? ### Expected behavior A few things are expected: 1. I should be able to download the phpList 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 s