|
Apache HTTPD
|
Classes | |
| struct | apr_md5_ctx_t |
Macros | |
| #define | APR_MD5_DIGESTSIZE 16 |
Typedefs | |
| typedef struct apr_md5_ctx_t | apr_md5_ctx_t |
Functions | |
| APU_DECLARE (apr_status_t) apr_md5_init(apr_md5_ctx_t *context) | |
Variables | |
| apr_xlate_t * | xlate |
| const void * | input |
| const void apr_size_t | inputLen |
| apr_md5_ctx_t * | context |
| const char * | salt |
| const char char * | result |
| const char char apr_size_t | nbytes |
| unsigned int | count |
| unsigned int const unsigned char apr_size_t | salt_len |
| unsigned int const unsigned char apr_size_t char * | out |
| unsigned int const unsigned char apr_size_t char apr_size_t | out_len |
| const char * | hash |
| APU_DECLARE | ( | apr_status_t | ) |
MD5 Initialize. Begins an MD5 operation, writing a new context.
| context | The MD5 context to initialize. |
MD5 translation setup. Provides the APR translation handle to be used for translating the content before calculating the digest.
| context | The MD5 content to set the translation for. |
| xlate | The translation handle to use for this MD5 context |
MD5 block update operation. Continue an MD5 message-digest operation, processing another message block, and updating the context.
| context | The MD5 content to update. |
| input | next message block to update |
| inputLen | The length of the next message block |
MD5 finalization. Ends an MD5 message-digest operation, writing the message digest and zeroing the context
| digest | The final MD5 digest |
| context | The MD5 content we are finalizing. |
MD5 in one step
| digest | The final MD5 digest |
| input | The message block to use |
| inputLen | The length of the message block |
Encode a password using an MD5 algorithm
| password | The password to encode |
| salt | The salt string to use for the encoding |
| result | The string to store the encoded password in |
| nbytes | The size of the result buffer |
Encode a password using the bcrypt algorithm
| password | The password to encode |
| count | The cost of the encoding, possible values are 4 to 31 |
| salt | Pointer to binary data to be used as salt for the encoding |
| salt_len | The size of the salt data (must be >= 16) |
| out | The string to store the encoded password in |
| out_len | The size of the result buffer (must be >= 61) |
Validate hashes created by APR-supported algorithms: md5, bcrypt, and sha1. hashes created by crypt are supported only on platforms that provide crypt(3), so don't rely on that function unless you know that your application will be run only on platforms that support it. On platforms that don't support crypt(3), this falls back to a clear text string comparison.
| passwd | The password to validate |
| hash | The password to validate against |
< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.
< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.
< Exclusive lock. Only one process may hold an exclusive lock at any given time. This is analogous to a "write lock".
< Exclusive lock. Only one process may hold an exclusive lock at any given time. This is analogous to a "write lock".
< Replace
< Insert with duplicates
< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.
< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.
< mask to extract lock type
< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.
< Exclusive lock. Only one process may hold an exclusive lock at any given time. This is analogous to a "write lock".
< Exclusive lock. Only one process may hold an exclusive lock at any given time. This is analogous to a "write lock".
< Size of the file
< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.
< Exclusive lock. Only one process may hold an exclusive lock at any given time. This is analogous to a "write lock".
Definition at line 358 of file apr_brigade.c.
| apr_md5_ctx_t* context |
| const void apr_size_t inputLen |
| unsigned int const unsigned char apr_size_t char apr_size_t out_len |
| apr_xlate_t* xlate |
1.9.8