security-and-privacy/gnupg
security-and-privacy
/
gnupg
mirror of git://git.gnupg.org/gnupg.git
1
0
Fork 0
Code Releases Activity

doc: Put the Unattended Usage of GPG section also into the man page. 

--
This commit is contained in:
Werner Koch 2023-02-16 15:07:40 +01:00
parent f118e3b101
commit 49fe6a2821
No known key found for this signature in database
GPG Key ID: E3FDFF218E45B72B
1 changed files with 17 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
doc/gpg.texi
View File

@ -4331,7 +4331,7 @@ already been reported to our bug tracker at @url{https://bugs.gnupg.org}.
@c *************** UNATTENDED ************** @c *************** UNATTENDED **************
@c *************** ************** @c *************** **************
@c ******************************************* @c *******************************************
@manpause @mansect notes
@node Unattended Usage of GPG @node Unattended Usage of GPG
@section Unattended Usage @section Unattended Usage
@ -4402,32 +4402,21 @@ previous subsection ``The quick key manipulation interface''.
The parameters for the key are either read from stdin or given as a The parameters for the key are either read from stdin or given as a
file on the command line. The format of the parameter file is as file on the command line. The format of the parameter file is as
follows: follows: Text only, line length is limited to about 1000 characters.
UTF-8 encoding must be used to specify non-ASCII characters. Empty
@itemize @bullet lines are ignored. Leading and trailing white space is ignored. A
@item Text only, line length is limited to about 1000 characters. hash sign as the first non white space character indicates a comment
@item UTF-8 encoding must be used to specify non-ASCII characters. line. Control statements are indicated by a leading percent sign,
@item Empty lines are ignored. their arguments are separated by white space from the keyword.
@item Leading and trailing white space is ignored. Parameters are specified by a keyword, followed by a colon; arguments
@item A hash sign as the first non white space character indicates are separated by white space. The first parameter must be
a comment line. @samp{Key-Type} but control statements may be placed anywhere. The
@item Control statements are indicated by a leading percent sign, the order of the parameters does not matter except for @samp{Key-Type}.
arguments are separated by white space from the keyword. The parameters are only used for the generated keyblock (primary and
@item Parameters are specified by a keyword, followed by a colon. Arguments subkeys); parameters from previous sets are not used. Some syntax
are separated by white space. checks may be performed. Key commences when either the end of the
@item parameter file is reached, the next @samp{Key-Type} parameter is
The first parameter must be @samp{Key-Type}; control statements may be encountered, or the control statement @samp{%commit} is encountered.
placed anywhere.
@item
The order of the parameters does not matter except for @samp{Key-Type}
which must be the first parameter. The parameters are only used for
the generated keyblock (primary and subkeys); parameters from previous
sets are not used. Some syntactically checks may be performed.
@item
Key generation takes place when either the end of the parameter file
is reached, the next @samp{Key-Type} parameter is encountered or at the
control statement @samp{%commit} is encountered.
@end itemize
@noindent @noindent
Control statements: Control statements:
@ -4463,7 +4452,7 @@ See the previous subsection ``Ephemeral home directories''.
@item %ask-passphrase @item %ask-passphrase
@itemx %no-ask-passphrase @itemx %no-ask-passphrase
This option is a no-op for GnuPG 2.1 and later. This option is a no-op since GnuPG version 2.1.
@item %no-protection @item %no-protection
Using this option allows the creation of keys without any passphrase Using this option allows the creation of keys without any passphrase