Lines Matching refs:and

24 associated with the key and provides operations to describe and destroy it.
28 A completely in-kernel key retention and operation subtype can be defined, but
30 a TPM) that might be used to both retain the relevant key and perform
37 subtype of the key and define the operations that can be done on that key.
49 the opportunity to pre-parse a key and to determine the description the key
101 and key identifier representations:
115 required for verification, but not currently supported, and others
116 (eg. decryption and signature generation) require extra key data.
128 The caller must have already obtained the key from some source and can then use
129 it to check the signature.  The caller must have parsed the signature and
143 The algorithm used must be noted in sig->pkey_hash_algo, and all the MPIs that
144 make up the actual signature must be stored in sig->mpi[] and the count of MPIs
147 In addition, the data must have been digested by the caller and the resulting
148 hash must be pointed to by sig->digest and the size of the hash be placed in
166 performed on that key and that determines what data is attached as the key
169 The subtype is selected by the key data parser and the parser must initialise
177 and looks like the following:
191 The owner and name fields should be set to the owning module and the name of
206      asymmetric key will look after freeing the fingerprint and releasing the
222 blob of data that holds the key data.  It would have to parse it and error
225 dates) and may contain useful data about the key (identifiers, capabilities).
244 and looks like the following:
253 The owner and name fields should be set to the owning module and the name of
256 There is currently only a single operation defined by the parser, and it is
261      This is called to preparse the key from the key creation and update paths.
263      allocated, and as such, is permitted to provide the key's description in
267      cleared, except for data, datalen and quotalen [see
279      The instantiation data is in a blob pointed to by data and is datalen in
281      all, and shouldn't change any of the other values _unless_ they are
282      recognise the blob format and will not return -EBADMSG to indicate it is
286      the key and attach it to ->description, ->type_data[0] should be set to
289      fingerprint and quotalen should be updated to indicate how much quota this
292      When clearing up, the data attached to ->type_data[1] and ->description
293      will be kfree()'d and the data attached to ->payload will be passed to the
303      public-key algorithm such as RSA and DSA this will likely be a printable
306 Functions are provided to register and unregister parsers: