aboutsummaryrefslogtreecommitdiffstats
path: root/doc/FAQ
diff options
context:
space:
mode:
authorWerner Koch <[email protected]>1999-07-14 17:47:23 +0000
committerWerner Koch <[email protected]>1999-07-14 17:47:23 +0000
commit40f2d9f830fc86435e4d408689cb4168892d7d4c (patch)
treed7b35f48495dcdc673133011b96e18162928280d /doc/FAQ
parentSee ChangeLog: Tue Jul 13 17:39:25 CEST 1999 Werner Koch (diff)
downloadgnupg-40f2d9f830fc86435e4d408689cb4168892d7d4c.tar.gz
gnupg-40f2d9f830fc86435e4d408689cb4168892d7d4c.zip
See ChangeLog: Wed Jul 14 19:42:08 CEST 1999 Werner Koch
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/FAQ b/doc/FAQ
index c57b490ae..c879f93aa 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -161,7 +161,7 @@
on a local computer (a disconnected laptop is probably the best choice)
and if you need it on your connected box (I know: We all do this) be
sure to have a strong password for your account and for your secret key
- and trust your Root.
+ and that you can trust your system administrator.
When I check GnuPG on a remote system via ssh (I have no Alpha here ;-)
I have the same problem. It takes a *very* long time to create the
@@ -178,7 +178,7 @@
You can see the validity (calculated trust value) using this command.
- gpgm --list-keys --with-colons
+ gpg --list-keys --with-colons
If the first field is "pub" or "uid", the second field shows you the trust:
@@ -199,7 +199,7 @@
You can get a list of the assigned trust values (how much you trust
the owner to correctly sign another person's key)
- gpgm --list-ownertrust
+ gpg --list-ownertrust
The first field is the fingerprint of the primary key, the second field
is the assigned value: