mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-02 22:46:30 +02:00
Various changes
This commit is contained in:
parent
4d770bedc1
commit
2e8481c03b
56 changed files with 527 additions and 337 deletions
|
@ -740,13 +740,23 @@ test whether the key is a valid key to sign something and responds with
|
|||
okay.
|
||||
|
||||
@example
|
||||
SETHASH <algo> <hexstring>
|
||||
SETHASH --hash=<name>|<algo> <hexstring>
|
||||
@end example
|
||||
|
||||
The client can use this command to tell the server about the data <hexstring>
|
||||
(which usually is a hash) to be signed. <algo> is the decimal encoded hash
|
||||
algorithm number as used by Libgcrypt.
|
||||
algorithm number as used by Libgcrypt. Either <algo> or --hash=<name>
|
||||
must be given. Valid names for <name> are:
|
||||
|
||||
@table @code
|
||||
@item sha1
|
||||
@item sha256
|
||||
@item rmd160
|
||||
@item md5
|
||||
@item tls-md5sha1
|
||||
@end table
|
||||
|
||||
@noindent
|
||||
The actual signing is done using
|
||||
|
||||
@example
|
||||
|
@ -754,19 +764,9 @@ The actual signing is done using
|
|||
@end example
|
||||
|
||||
Options are not yet defined, but my later be used to choosen among
|
||||
different algorithms (e.g. pkcs 1.5)
|
||||
|
||||
The agent does then some checks, asks for the passphrase and
|
||||
if SETHASH has not been used asks the client for the data to sign:
|
||||
|
||||
@example
|
||||
S: INQUIRE HASHVAL
|
||||
C: D ABCDEF012345678901234
|
||||
C: END
|
||||
@end example
|
||||
|
||||
As a result the server returns the signature as an SPKI like S-Exp
|
||||
in "D" lines:
|
||||
different algorithms. The agent does then some checks, asks for the
|
||||
passphrase and as a result the server returns the signature as an SPKI
|
||||
like S-expression in "D" lines:
|
||||
|
||||
@example
|
||||
(sig-val
|
||||
|
|
|
@ -13,7 +13,11 @@ to GnuPG etc.
|
|||
|
||||
** Explain how to setup a root CA key as trusted
|
||||
** Explain how trustlist.txt might be managed.
|
||||
|
||||
** How to get the ssh support running
|
||||
How to use the ssh support.
|
||||
|
||||
|
||||
@section Installation Overview
|
||||
|
||||
|
||||
|
||||
|
|
|
@ -66,6 +66,9 @@ any security audit and you should not use any valuable private key. In
|
|||
particular, @strong{using it on a box with more than one user, might
|
||||
lead to a key compromise}.
|
||||
|
||||
@strong{It is quite possible that the current version does not even
|
||||
build.}
|
||||
|
||||
@noindent
|
||||
Current limitations are:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue