KEYS: Preparse match data
authorDavid Howells <dhowells@redhat.com>
Tue, 16 Sep 2014 16:36:02 +0000 (17:36 +0100)
committerDavid Howells <dhowells@redhat.com>
Tue, 16 Sep 2014 16:36:02 +0000 (17:36 +0100)
commit462919591a1791e76042dc5c1e0148715df59beb
tree44a60ee5f08eab18b1a69f98d993f9a47a45fece
parent53d91c5ce0cb8945b55e8bb54e551cabc51eb28d
KEYS: Preparse match data

Preparse the match data.  This provides several advantages:

 (1) The preparser can reject invalid criteria up front.

 (2) The preparser can convert the criteria to binary data if necessary (the
     asymmetric key type really wants to do binary comparison of the key IDs).

 (3) The preparser can set the type of search to be performed.  This means
     that it's not then a one-off setting in the key type.

 (4) The preparser can set an appropriate comparator function.

Signed-off-by: David Howells <dhowells@redhat.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
crypto/asymmetric_keys/asymmetric_type.c
include/keys/user-type.h
include/linux/key-type.h
net/dns_resolver/dns_key.c
security/keys/internal.h
security/keys/keyring.c
security/keys/proc.c
security/keys/process_keys.c
security/keys/request_key.c
security/keys/request_key_auth.c
security/keys/user_defined.c
This page took 0.030255 seconds and 5 git commands to generate.