ceos/cagebreak
1
0
Fork 0
mirror of https://cagebreak.project-repo.co/cagebreak.git synced 2026-08-24 06:24:19 +02:00
Code Issues Projects Releases Packages Wiki Activity

Add new gpg keys.

Browse source
This commit is contained in:
project-repo 2024-01-03 17:00:25 +01:00
commit f0217900f5
10 changed files with 334 additions and 95 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/dev-FAQ.md
View file

@ -48,3 +48,18 @@ License, contributors etc. should be appropriate.
Shellcheck must pass on any script (judicious use of shellcheck pragmas is allowed but
discouraged).
## How do I add a new gpg key?
1. Check which gpg key versions are currently valid.
2. Generate keys with incremented numbers/emails/dates/passphrase.
* Use 4096 Bit RSA Keys
3. Sign the new keys with at least one then-old signing key.
4. Genereate new cagebreak@project-repo.co key
5. Sign the new mail key with the new signing keys.
6. Generate new pkgbuild key.
7. Sign the pkgbuild key with the new signing keys.
8. Add public keys to `keys/`.
9. Update meson_options.txt
10. Update [all man pages](../manuals.md), [CONTRIBUTING](../CONTRIBUTING.md) & [SECURITY.md](../SECURITY.md)
11. Update the pkgbuild repo with the new key (key and readme).
12. Securely distribute private keys and revocation certificates as per the internal wiki.