Next: Miscellaneous UI Server Commands, Previous: UI Server: Managing certificates., Up: The GnuPG UI Server Protocol [Contents][Index]
First, the input files need to be specified by one or more
FILE
commands. Afterwards, the actual operation is requested:
Request that checksums are created for the files specified by
FILE
. The choice of checksum algorithm and the destination
storage and format for the created checksums depend on the preferences
of the user and the functionality provided by the UI server. For
directories, the server may offer multiple options to the user (for
example ignore or process recursively).
The option --nohup
is mandatory. It is currently unspecified
what should happen if --nohup
is not present. Because
--nohup
is present, the server always returns OK
promptly, and completes the operation asynchronously.
Request that checksums are created for the files specified by
FILE
and verified against previously created and stored
checksums. The choice of checksum algorithm and the source storage
and format for previously created checksums depend on the preferences
of the user and the functionality provided by the UI server. For
directories, the server may offer multiple options to the user (for
example ignore or process recursively).
If the source storage of previously created checksums is available to
the user through the Windows shell, this command may also accept such
checksum files as FILE
arguments. In this case, the UI server
should instead verify the checksum of the referenced files as if they
were given as INPUT files.
The option --nohup
is mandatory. It is currently unspecified
what should happen if --nohup
is not present. Because
--nohup
is present, the server always returns OK
promptly, and completes the operation asynchronously.
Next: Miscellaneous UI Server Commands, Previous: UI Server: Managing certificates., Up: The GnuPG UI Server Protocol [Contents][Index]