GPG signatures for source validation

[NicoHood]

As we all know, today more than ever before, it is crucial to be able to trust our computing environments. One of the main difficulties that package maintainers of Linux distributions face, is the difficulty to verify the authenticity and the integrity of the source code.

The Mooltipass users would appreciate it if you would provide us GPG signatures in order to verify easily and quickly of your source code releases.

Overview of the required tasks:

• [ ] Please create and/or use a 4096-bit RSA keypair for the file signing
• The key may be used for email encryption too
• Keep your key secret, use a strong unique passphrase for the key
• [ ] Upload the public key to a key server
• [ ] Sign every new commit by default
• [ ] Sign new tags
• Verify the Github Release tarball download against your local source
• [ ] Sign Github Release tarballs

Additional Information:

• https://help.github.com/categories/gpg/
• https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work
• https://www.qubes-os.org/doc/verifying-signatures/
• https://developers.google.com/web/fundamentals/security/encrypt-in-transit/why-https

Thanks.

[limpkin]

We might do that when the official firmware for the mini is released.

[NicoHood]

Your commits are still not signed yet. Please do so, the earlier you start, the better it is. It is super easy to sign git commits: https://github.com/NicoHood/NicoHood.github.io/wiki/How-to-sign-sources-with-GPG-in-under-5-minutes