[WIP][progamming][packaging] Sign PKGBUILD packages

and the repository metadata with a GPG key.

src/programming/packaging.rst

@@ -3,6 +3,44 @@ Packaging
 
 .. contents:: Table of Contents
 
+GPG Keys
+--------
+
+Creation
+~~~~~~~~
+
+Signing a binary package with a GPG key ensures that it has not been tampered with. DEB, PKGBUILD, and RPM packages all support signing with a GPG public and private key pair.
+
+-  Create a GPG key pair. It will be saved to ``~/.gnupg/``. Either use the defaults by running ``gpg --gen-key`` or ``gpg --full-generate-key`` to configure all of the options including the encryption type, bit size, and expiration time.
+
+   .. code-block:: sh
+
+      $ gpg --gen-key
+      Real name: <FIRST_NAME> <LAST_NAME>
+      Email address: <EMAIL_ADDRESS>
+      You selected this USER-ID:
+          "<FIRST_NAME> <LAST_NAME> <EMAIL_ADDRESS>"
+
+-  Find the GPG key ID and use it to generate a plaintext public key file. [31]
+
+   .. code-block:: sh
+
+      $ gpg --list-keys
+      $ gpg --export --armor <GPG_KEY_ID> > ~/.gnupg/gpg-public-key.asc
+
+-  Optionally send the GPG key to a remote server. Verify that it was uploaded.
+
+   .. code-block:: sh
+
+      $ gpg --send-keys <GPG_KEY_ID>
+      $ gpg --recv-keys <GPG_KEY_ID>
+
+https://www.sainnhe.dev/post/create-personal-arch-linux-package-repository/
+
+<KEY SERVER DOCS HERE>
+
+https://www.arcolinuxiso.com/create-a-key-to-sign-your-packages/
+
 DEB (Debian)
 ------------
 
@@ -540,24 +578,7 @@ Build the binary RPM(s). The RPM(s), along with the log files, will be stored at
 GPG Signing
 ^^^^^^^^^^^
 
-Signing a binary RPM package with a GPG key ensures that it has not been tampered with.
-
--  Create a GPG key pair. It will be saved to ``~/.gnupg/``.
-
-   .. code-block:: sh
-
-      $ gpg --gen-key
-      Real name: <FIRST_NAME> <LAST_NAME>
-      Email address: <EMAIL_ADDRESS>
-      You selected this USER-ID:
-          "<FIRST_NAME> <LAST_NAME> <EMAIL_ADDRESS>"
-
--  Find the GPG key ID and use it to generate a plaintext public key file. [31]
-
-   .. code-block:: sh
-
-      $ gpg --list-keys
-      $ gpg --export --armor <GPG_KEY_ID> > ~/.gnupg/gpg-public-key.asc
+-  `Create <#creation>`__ a GPG key pair.
 
 -  Import the GPG key on all of the systems that will install the signed RPMs.
 
@@ -790,6 +811,9 @@ PKGBUILD (Arch Linux)
 Creating a PKGBUILD
 ~~~~~~~~~~~~~~~~~~~
 
+PKGBUILD File
+^^^^^^^^^^^^^
+
 Arch Linux packages are design to be simple and easy to create. A
 PKGBUILD file is compressed with a software's contents into a XZ
 tarball. This can contain either the source code or compiled program.
@@ -869,6 +893,52 @@ Required:
 
 [10][11]
 
+GPG Signing
+^^^^^^^^^^^
+
+-  `Create <#creation>`__ a GPG key pair. Even if this key is added and signed by the ``pacman-key`` command later on, the local user needs access to the GPG key. Otherwise, ``makepkg`` or ``repo-add`` will complain that the GPG key ID does not exist. [35]
+-  Import a GPG public key file, load the key, and then verify that it has been imported. [36]
+
+   .. code-block:: sh
+
+      $ sudo pacman-key --add ~/.gnupg/gpg-public-key.asc
+      $ pacman-key --list-keys
+      $ sudo pacman-key --init
+      $ sudo pacman-key --lsign-key <GPG_KEY_ID>
+
+**Build and Sign Packages**
+
+-  Configure ``makepkg`` to sign packages by default.
+
+   .. code-block:: sh
+
+      $ sudo -E ${EDITOR} /etc/makepkg.conf
+      BUILDENV=(!distcc color !ccache check sign)
+      PACKAGER="<FIRST_NAME> <LAST_NAME> <EMAIL_ADDRESS>"
+      GPGKEY="<GPG_KEY_ID>"
+
+-  Or manually run ``makepkg --sign --key <GPG_KEY_ID>``.
+
+-  Force the repository metadata to be updated to use the GPG key. [37][38][39]
+
+   .. code-block:: sh
+
+      $ repo-add --verify --sign
+
+**Sign Existing Packages**
+
+-  Create a detatched GPG signature.
+
+   .. code-block:: sh
+
+      $ gpg --detach-sign --no-armor <PACKAGE>
+
+-  Force the repository metadata to be updated to use the GPG key. [40]
+
+   .. code-block:: sh
+
+      $ repo-add --verify --sign
+
 AUR Submission
 ~~~~~~~~~~~~~~
 
@@ -912,6 +982,48 @@ There should not be any binary or source code hosted in the AUR git repository.
 
 [13]
 
+Troubleshooting
+~~~~~~~~~~~~~~~
+
+::
+
+   ==> ERROR: The key 0AFB9B4386ADE78AF9117ABD6C281AB5ED6DB01E does not exist in your keyring.
+
+Solution:
+
+-  The GPG key exists for a different user. [35] Export the private GPG key and then import it.
+
+   .. code-block:: sh
+
+      $ gpg --list-secret-keys
+      $ gpg --export-secret-keys <GPG_KEY_ID> > /tmp/gpg-private.key
+      $ chown <OTHER_USER> /tmp/gpg-private.key
+      $ su - <OTHER_USER>
+      $ gpg --import /tmp/gpg-private.key
+      $ rm -f /tmp/gpg-private.key
+
+https://makandracards.com/makandra-orga/37763-gpg-extract-private-key-and-import-on-different-machine
+
+----
+
+::
+
+   $ gpg --import <GPG_KEY_FILE>.asc
+   gpg: key 1c424e039f4444af: "<FIRST_NAME> <LAST_NAME> <EMAIL_ADDRESS>" not changed
+   gpg: key 1c424e039f4444af/bec914517aa203f3: error sending to agent: Permission denied
+   gpg: key 1c424e039f4444af/bec914517aa203f3: error sending to agent: Permission denied
+   gpg: error reading '<GPG_KEY_FILE>.asc': Permission denied
+   gpg: import from '<GPG_KEY_FILE>.asc' failed: Permission denied
+   gpg: Total number processed: 0
+   gpg:              unchanged: 1
+   gpg:       secret keys read: 1
+
+Solution:
+
+-  GPG needs to be able to access the TTY to get standard input for the GPG key password. The easiest way to do this is to start a ``screen`` or ``tmux`` session. Then run the ``gpg --import`` command again.
+
+https://github.com/coolacid/docker-misp/issues/33
+
 History
 -------
 
@@ -957,3 +1069,9 @@ Bibliography
 32. "Signing and Creating a Repository for RPM Packages." CDOT Wiki. July 17, 2017. Accessed August 14, 2023. https://hussainaliakbar.github.io/signing-and-verifying-rpm-packages/
 33. "Signing and Verifying RPM Packages." Hussain Ali Akbar. April 25, 2018. Accessed August 14, 2023. https://wiki.cdot.senecacollege.ca/wiki/Signing_and_Creating_a_Repository_for_RPM_Packages
 34. "Creating and hosting your own rpm packages and yum repo." Earthly. June 24, 2021. Accessed August 14, 2023. https://earthly.dev/blog/creating-and-hosting-your-own-rpm-packages-and-yum-repo/
+35. "SOLVED: makepkg fails at signing package." Arch Linux Forums. May 25, 2012. Accessed August 16, 2023. https://bbs.archlinux.org/viewtopic.php?id=142128
+36. "pacman-key Command Examples." The Geek Diary. Accessed August 16, 2023. https://www.thegeekdiary.com/pacman-key-command-examples/
+37. "DeveloperWiki:Package signing." ArchWiki. September 25, 2022. Accessed August, 2023. https://wiki.archlinux.org/title/DeveloperWiki:Package_signing
+38. "pacman/Package signing." ArchWiki. August 13, 2023. Accessed August 16, 2023. https://wiki.archlinux.org/title/Pacman/Package_signing
+39. "Pacman Package Signing – 1: Makepkg and Repo-add." Allan McRae. August 7, 2011. Accessed August 16, 2023. http://allanmcrae.com/2011/08/pacman-package-signing-1-makepkg-and-repo-add/
+40. "pacman-sign-guide." GitHub Gist elieux/guide.md. October 4, 2015. Accessed August 16, 2023. https://gist.github.com/elieux/fad9451bbfc4ddb5cde7