Lines Matching refs:purposes
398 For the purposes of this library, the term \textit{byte} will refer to an octet or eight bit word. Typically an array of
492 cipher descriptors may require to be called for resource management purposes. To be compliant, all functions which call a cipher
653 fact used for the purposes of encryption. My suggestion is just to use random 8/24 byte keys instead of trying to make a 8/24
2068 It is highly recommended that you \textbf{not} use the MD4 or MD5 hashes for the purposes of digital signatures or authentication codes.
2069 These hashes are provided for completeness and they still can be used for the purposes of password hashing or one-way accumulators
2073 for all purposes you would normally use a hash for.
2202 CMAC within NIST, for the purposes of this library OMAC and CMAC are synonymous. From an API standpoint, the OMAC routines work much like the
2584 If the user simply wants a MAC function (hint: use OMAC) padding with a single 0x40 byte should be sufficient for security purposes and still be reasonably compatible
4766 In order to securely handle user passwords for the purposes of creating session keys and chaining IVs the PKCS \#5 was drafted. PKCS \#5
