Skip to content

Fix terminology and clarity in GPG keys section #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
stefan-wenig wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix terminology and clarity in GPG keys section #52

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/managing-certificates.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,16 +29,16 @@ With SignPath, you have the following options for creating or importing a certif
>
> {% include editions.md feature="no_display.gpg_key_management" %}
>
> In the world of GPG, certificates are known under various names:
> In the world of GPG, certificates are known by various names:
>
> * Certificate or Transferable Public Keys according to [OpenPGP](https://datatracker.ietf.org/doc/html/rfc4880)
> * GPG keys or GPG public keys in everyday usage (which can be confusing as _public key_ usually means the public part of an asymmetfic cryptographic key pair)
> * Certificate or Transferable Public Key according to the [OpenPGP specification](https://datatracker.ietf.org/doc/html/rfc4880)
> * GPG keys or GPG public keys in everyday usage (which can be confusing as _public key_ usually means the public part of an asymmetric cryptographic key pair)
>
> SignPath uses the term _GPG key_ to denote this type of _Certificate_.
>
> These terms all refer to a specific file format that includes the actual public key, the key holder's identity (name and email address), expiration, and other data.
> These terms all refer to a specific file format that includes the actual public key, the key holder's identity (name and email address), expiration information, and other data.
>
> Unlike X.509, GPG does not define a Public Key Infrastructure (PKI) based on Certificate Authoities (CAs). Instead, GPG certificates are usually provided as downloads on a separate channel and/or published on an [OpenPGP Key server](https://en.wikipedia.org/wiki/Key_server_(cryptographic)).
> Unlike X.509, GPG does not define a Public Key Infrastructure (PKI) based on Certificate Authorities (CAs). Instead, GPG certificates are usually provided as downloads on a separate channel and/or published on an [OpenPGP Key server](https://en.wikipedia.org/wiki/Key_server_(cryptographic)).

## Restrictions

Expand Down