Document GPG key usage #127

There is no content yet.

I feel like there should be some screenshots, also what should the numbers be?

3. Enter you desired key size, it must be at least [TODO Number of bits], press enter to confirm
4. Choose the amount of time you want it to be valid for, we recommend [TODO length of time] for increased security, however you can type 0 for it to never expire. Press enter to confirm.

I think 4096 bits and 1-2 years would be appropriate. Though I'm not sure if the former is a requirement.

maybe "we recommend" instead of "it must be at lest"?

maybe "we recommend" instead of "it must be at lest"?

On GitHub they have a minimum key length, so I assumed codeberg did too

https://docs.gitea.io/en-us/signing/ looks like Gitea only checks if the signature matches the one a user uploaded and not much more. So I'd say you can go for "recommend"

Some syntax changes.

@unbeatable-101 thank you for coming up and finishing this, I pretty much like it. I think most reviewed points are valid, let's improve and finalize this :-)

@n thank you as always for your quite detailed review. I don't have that strong feelings to some suggestions, I'll have a closer look to this PR once you discussed out this stuff 😉

Note in 55eb9796a5 your change from OSX to mac OS got lost. It's actually unrelated to this PR, this is a good example of why not to touch stuff that is unrelated, it might get mixed up or lost when you don't recall you did it.

Not sure if you just want to readd this commit or create a new PR (or don't care). I'm fine with all solutions this time.

Yeah that was perposeful that I didn't re-add it since it was unrelated

Thanks for finishing the guide and implementing all of my suggestions. Other than a minor issue, we are ready to merge.

Damn, manual merges suck. Autodetection is disabled and you can only set a manual merge after you have a commit, but you can't set it as manually merged, when there are conflicts. Of course, a manual merge commit creates conflicts. Arrrgghhh.

Sorry. I guess I will simply close this.

 . Download and install [GnuGPG](https://gnupg.org/download/index.html#binary).<blockquote>If you are using a linux distro this might already be installed, check by typing `gpg` in the terminal.</blockquote>
 . Type `gpg --list-secret-keys --keyid-format LONG` into your terminal, it will list all the keys that you have both a public and private key for.
 . Check the output for a key that you want, if there are none, or none that you want to use, continue to [Generating a GPG key](#toc_2). If there is one that you want to use, skip to [adding it to your account](#Adding-to-Codeberg).
 <blockquote>

 sec   4096R/3AA5C34371567BD2 2016-03-10 [expires: 2017-03-10]
 uid                          Hubot
 ssb   4096R/42B317FD4BA89E7A 2016-03-10
 ```

 ```
 . Type `gpg --armor --export <GPG KEY ID>` into the terminal
 . Copy the output including the `-----BEGIN PGP PUBLIC KEY BLOCK-----` and `-----END PGP PUBLIC KEY BLOCK-----`
 . Go to [https://codeberg.org/user/settings/keys](https://codeberg.org/user/settings/keys)

 . Type `gpg --armor --export <GPG KEY ID>` into the terminal
 . Copy the output including the `-----BEGIN PGP PUBLIC KEY BLOCK-----` and `-----END PGP PUBLIC KEY BLOCK-----`
 . Go to [https://codeberg.org/user/settings/keys](https://codeberg.org/user/settings/keys)
 . Press `Add Key` in the `Manage GPG Keys` section

 . Choose the amount of time you want it to be valid for, we recommend 1-2 years for increased security, however you can type 0 for it to never expire. Press enter to confirm.
 . Verify your selections are correct, type `y` and press enter to confirm
 . Enter your information, be sure to use the same email as your Codeberg account
 . Type in a passphrase, make sure you write it down somewhere safe. You'll need it later to add your key to git or revoke it if it is compromised


			`"Knut the Polar Bear" has been derived from https://openclipart.org/detail/193243/polar-bear-remix, under CC0 1.0`

			`Parts of [content/security/gpg-key.md](content/security/gpg-key.md) have been derived from [docs.github.com](https://docs.github.com), under CC-BY 4.0`

 ---
 ## What is a GPG key?
 GPG stands for GNU Privacy Guard, an opensource implementation of the [Open PGP](https://en.wikipedia.org/wiki/Pretty_Good_Privacy#OpenPGP) protocol. A GPG key is used to sign each commit you make so your collaborators can be sure it was you who made it.

 ## Adding an Existing GPG key
 If you have your public key in an easy to find location, great! You can skip to [adding it to your account](#Adding-to-Codeberg). If not we will be using the [GnuPG software](https://gnupg.org/download/index.html#binary) to check, if you have downloaded this before you can skip to [Generating a GPG key](#Generating).
 . Download and install [GnuGPG](https://gnupg.org/download/index.html#binary).<blockquote>If you are using a linux distro this might already be installed, check by typing `gpg` in the terminal.</blockquote>

 . Type `gpg --full-generate-key` into your terminal
 . Type `1` and press enter to select `RSA and RSA`
 . Enter you desired key size, it should be at least 4096 bits, as lower values are insecure, press enter to confirm

 . Type `gpg --list-secret-keys --keyid-format LONG` into the terminal
 . Select the key you would like to use (the one you just generated). In this example, the GPG key ID is `3AA5C34371567BD2`:
 ```

 </blockquote>
 <h2 id=Generating>Generating a GPG key</h2>
 If you haven’t already, be sure to [install](https://gnupg.org/download/index.html#binary) GnuPGP, as we you will be using it to generate your keys.

Document GPG key usage #127

Reviewers