diff options
author | David Howells <dhowells@redhat.com> | 2012-09-22 00:25:04 +0200 |
---|---|---|
committer | Rusty Russell <rusty@rustcorp.com.au> | 2012-10-08 05:20:15 +0200 |
commit | 4ae71c1dce1e3d2270a0755988033e236b8e45d6 (patch) | |
tree | dd48fafaa13f718a7ea0a9e0fa79e8211239fe8e /lib/sha1.c | |
parent | KEYS: Asymmetric public-key algorithm crypto key subtype (diff) | |
download | linux-4ae71c1dce1e3d2270a0755988033e236b8e45d6.tar.xz linux-4ae71c1dce1e3d2270a0755988033e236b8e45d6.zip |
KEYS: Provide signature verification with an asymmetric key
Provide signature verification using an asymmetric-type key to indicate the
public key to be used.
The API is a single function that can be found in crypto/public_key.h:
int verify_signature(const struct key *key,
const struct public_key_signature *sig)
The first argument is the appropriate key to be used and the second argument
is the parsed signature data:
struct public_key_signature {
u8 *digest;
u16 digest_size;
enum pkey_hash_algo pkey_hash_algo : 8;
union {
MPI mpi[2];
struct {
MPI s; /* m^d mod n */
} rsa;
struct {
MPI r;
MPI s;
} dsa;
};
};
This should be filled in prior to calling the function. The hash algorithm
should already have been called and the hash finalised and the output should
be in a buffer pointed to by the 'digest' member.
Any extra data to be added to the hash by the hash format (eg. PGP) should
have been added by the caller prior to finalising the hash.
It is assumed that the signature is made up of a number of MPI values. If an
algorithm becomes available for which this is not the case, the above structure
will have to change.
It is also assumed that it will have been checked that the signature algorithm
matches the key algorithm.
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Diffstat (limited to 'lib/sha1.c')
0 files changed, 0 insertions, 0 deletions