summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@sequoia-pgp.org>2021-10-30 11:56:04 +0300
committerLars Wirzenius <liw@sequoia-pgp.org>2021-10-30 11:56:04 +0300
commitadfbf93e5dba330e0a0092b30dabd22b74decd26 (patch)
tree45e7c4aea19d7ce8231eb7a8878b8ead430b5d7b
parent9e98ac46b908bbb67220bebef474a6a83fc1eb93 (diff)
downloadsq-user-guide-adfbf93e5dba330e0a0092b30dabd22b74decd26.tar.gz
move keyring intro out of section
-rw-r--r--sq-guide.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/sq-guide.md b/sq-guide.md
index 4cf5f7d..340c306 100644
--- a/sq-guide.md
+++ b/sq-guide.md
@@ -768,15 +768,15 @@ specifics that have been covered in the rest of the book.
This appendix is aimed at people who already know how to use `gpg`,
the command line tool from GnuPG that roughly corresponds to `sq`. It
shows how to do specific tasks using either `gpg` or `sq`. It will
-possibly be a comparison table, for easy review.
-## Generate a key and certificate
+GnuPG stores keys and certificates in the `~/.gnupg` directory, or
+directory named in the `GNUPGHOME` environment variable. They're not
+easily accessed directly as files, and are referred to via the user id
+or using a hexadecimal key identifier or key finger print. The set of
+keys and certificates in that directory is called a _keyring_. possibly
+be a comparison table, for easy review.
-Keys are stored in `~/.gnupg` or directory named in the `GNUPGHOME`
-environment variable. They're not easily access directly as files, and
-are referred to via a pattern for the user id or using a hexadecimal
-key identifier or key finger print. The set of keys and certificates
-in that directory is called a keyring.
+## Generate a key and certificate
```
gpg --quick-gen-key "Tomjon <tomjon@example.com>"
@@ -819,7 +819,7 @@ The first word of the line tells you what the line contains:
* `pub`---a public key (i.e., certificate)
* `sec`---a secret key (i.e., key, in `--list-secret-keys` output)
-* `sec#`---a secret key that isn't actually in the keyring
+* `sec#`---a secret key is known to exist, but isn't actually in the keyring
* `uid`---a userid attached to the key
* `sub`---a sub key