Hello Werner and list, While reading that FAQ top to bottom, I encountered some typo's which I fixed. I'm only used to git in a non-distributed fashion, so I'm not accustomed to it's patch submission features and simply attach a git-generated diff against 0968808. I hope that suffises.
And perhaps this needs clarification: > The fingerprint may also be given without the spaces in which case > there is no need for the quotes. If you want to sign only certain > user ids of a key, list those user id verbatim after the > fingerprint. When I read this, I think, do I need this: $ gpg2 --quick-sign-key '15CB 723E 2000 A1A8 2505 F3B7 CC00 B501 BD19 AC1C Daniel Ellsberg <ellsb...@example.org>' Or do I need this: $ gpg2 --quick-sign-key '15CB 723E 2000 A1A8 2505 F3B7 CC00 B501 BD19 AC1C' 'Daniel Ellsberg <ellsb...@example.org>' In other words, is it one argument or two arguments? I'd be inclined to the latter when thinking how I would design this, but I'm inclined to the former by the phrasing "after the fingerprint". An example would remove ambiguity. HTH, Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at <http://digitalbrains.com/2012/openpgp-key-peter>
diff --git a/web/faq/whats-new-in-2.1.org b/web/faq/whats-new-in-2.1.org index e5e6f71..e68969f 100644 --- a/web/faq/whats-new-in-2.1.org +++ b/web/faq/whats-new-in-2.1.org @@ -193,7 +193,7 @@ is still very limited. Thus GnuPG 2.1 currently hides the options to create an ECC key. For those who want to experiment with ECC or already want to prepare a -key for future use, the command =--gen-full-key= along with the option +key for future use, the command =--full-gen-key= along with the option =--expert= is the enabler: #+begin_example @@ -374,7 +374,7 @@ pub rsa2048/BD19AC1C In case the key has already been signed, the command prints a note and exits with success. In case you want to check that it really worked, -use ==--check-sigs= as usual: +use =--check-sigs= as usual: #+begin_example $ gpg2 --check-sigs '15CB 723E 2000 A1A8 2505 F3B7 CC00 B501 BD19 AC1C' @@ -497,18 +497,18 @@ For load balancing reasons, keyservers are organized in pools to enable instant round-robin DNS assignment of random keyservers. A problem with that approach is that the DNS resolver is not aware of the state of the keyserver. If a keyserver has gone down or a routing -problems occurs, /gpg/ and its keyserver helpers were not ware of it +problems occurs, /gpg/ and its keyserver helpers were not aware of it and would try over and over to use the same, dead, keyserver up until the DNS information expires and a the DNS resolver assigned a new server from the pool. The new /dirmngr/ in GnuPG does not use the implicit round-robin of -the DNS resolver but uses its own DNS look up and keeps an internal +the DNS resolver but uses its own DNS lookup and keeps an internal table of all hosts from the pool along with the encountered aliveness state. Thus after a failure (timeout) of a request, /dirmngr/ flags a host as dead and randomly selects another one from the pool. After a few hours the flag is removed so that the host will be tried again. -It is also possible to mark a specif host from a pool explicitly as +It is also possible to mark a specific host from a pool explicitly as dead so that it wonât be used in future. To interact with the /dirmngr/ the =gpg-connect-agent= tool is used: @@ -582,12 +582,12 @@ revocation certificate are put at the top of the file. :END: The /scdaemon/, which is responsible for accessing smardcards and -other tokens, has received many updates. In particular plugable USB +other tokens, has received many updates. In particular pluggable USB readers with a fixed card now work smoothless and similar to standard readers. The latest features of the [[http://www.fsij.org/doc-gnuk/][gnuk]] token are supported. Code for the SmartCard-HSM has been added. More card readers with a PIN pad are supported. The internal CCID driver does now also work with -certain non-auto configuration equipped readers. +certain non-auto-configuration equipped readers. ** New format for key listings :PROPERTIES: @@ -618,7 +618,7 @@ that is =show-uid-validity= is implicitly used for the The annotated key listing produced by the =--with-colons= options did not change. However a couple of new fields have been added, for -example if the new option =--with-secret-= is used the âS/N of a token +example if the new option =--with-secret= is used the âS/N of a token fieldâ indicates the presence of a secret key even in a public key listing. This option is supported by recent [[https://gnupg.org/related_software/gpgme/][GPGME]] versions and makes writing of key manager software easier. @@ -645,7 +645,7 @@ menu of /gpgsm/. In batch mode the certificate creation dialog can now be controlled by a parameter file with several new keywords. Such a parameter file allows the creation of arbitrary X.509 certificates similar to what -can be done with /openssl/. It may this be used as the base for a CA +can be done with /openssl/. It may thus be used as the base for a CA software. For details see the âCSR and certificate creationâ section in the manual.
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
