security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-03 22:56:33 +02:00
Code Activity

all: fix more spelling errors

Browse source
This commit is contained in:
Daniel Kahn Gillmor 2018-10-25 16:52:58 -04:00
parent b39ece7d35
commit a7c5d65eb5
19 changed files with 43 additions and 43 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/Notes
View file

@ -1,5 +1,5 @@
Add an infor page for watchgnupg.
Add an info page for watchgnupg.
> * How to mark a CA certificate as trusted.
@ -57,7 +57,7 @@ or
In general you should first import the root certificates and then down
to the end user certificate. You may put all into one file and gpgsm
will do the right thing in this case independend of the order.
will do the right thing in this case independent of the order.
While verifying a signature, all included certificates are
automagically imported.
@ -82,7 +82,7 @@ you get an output like:
uid:::::::::CN=Werner Koch,OU=test,O=g10 Code,C=de::
uid:::::::::<wk@g10code.de>::
This should be familar to advanced gpg-users; see doc/DETAILS in gpg
This should be familiar to advanced gpg-users; see doc/DETAILS in gpg
1.3 (CVS HEAD) for a description of the records. The value in the
"grp" tagged record is the so called keygrip and you should find a
file ~/.gnupg/private-keys-v1.d/C92DB9CFD588ADE846BE3AC4E7A2E1B11A4A2ADB.key