Lines Matching defs:in

8  * use in the OpenSSL Toolkit (http://www.openssl.org/).
17 * Redistribution and use in source and binary forms, with or without
24 * 2. Redistributions in binary form must reproduce the above copyright
25 * notice, this list of conditions and the following disclaimer in
32 * for use in the OpenSSL Toolkit. (http://www.OpenSSL.org/)"
40 * nor may "OpenSSL" appear in their names without prior written
46 * for use in the OpenSSL Toolkit (http://www.OpenSSL.org/)"
142 * As stated in v2.20, 11.7 Object Management Function, in section for
144 * time in a given session. Therefore, C_Find{,Init,Final}Objects() should be
151 * says that one thread can be in the middle of a search operation while another
152 * thread destroys the object matching the search template which would result in
162 * PK11_SESSION structure, either held by a thread or present in free_session
168 * Create all secret key objects in a global session so that they are available
239 /* These functions are also used in other files */
243 /* active list manipulation functions used in this file */
281 const unsigned char *in, size_t inl);
349 * Rows must be kept in sync with enum pk11_cipher_id.
388 * Rows must be kept in sync with enum pk11_digest_id.
401 * Structure to be used for the cipher_data/md_data in
402 * EVP_CIPHER_CTX/EVP_MD_CTX structures in order to use the same pk11
403 * session in multiple cipher_update calls
770 * symbol names to bind to. We set it in the Configure script based on whether
775 /* Needed in e_pk11_pub.c as well so that's why it is not static. */
946 * which in turn calls bn_mod_exp. Since we do not implement bn_mod_exp
1052 * same situation as in parent - we need to unlock all locks to make them
1087 * This is to prevent double free in the unlucky scenario:
1125 * pk11_library_initialized is set to 0 in pk11_finish() which is called
1131 * reinitialized in the child, forgotten functional reference causes
1141 * free the locks first to prevent memory leak in case
1210 * The library we use, set in def_PK11_LIBNAME, may not offer any
1338 * immediately if not. This is necessary in case a process finishes
1514 * Will use it to find out if we forked. We cannot use the PID field in
1619 * We will keep the session in the cache list and let
1658 * freed in pk11_get_session() as part of the post-fork clean up the
1720 * sessions as possible but any failure in C_CloseSession() means that we
1920 * objects in the free list.
2009 * objects in the free list.
2080 * if session is NULL, try to destroy all objects in the free list
2126 * stored in the keystore. Also, we always use read-only sessions so
2208 * counter block, see RFC 3686. If needed in the future, we can
2260 * iv_len in the ctx->cipher structure is the maximum IV length for the
2261 * current cipher and it must be less or equal to the IV length in our
2262 * ciphers table. The key length must be in the allowed interval. From
2264 * key length to be in some range, all other NIDs have a precise key
2268 * Note that the reason why the IV length in ctx->cipher might be
2295 * context that was finalized in pk11_cipher_cleanup().
2346 * When reusing the same key in an encryption/decryption session for a
2348 * and recreate a new one. Note that the key is in the global session so
2352 * development, these two functions in the PKCS#11 libraries used return
2353 * unexpected errors when passing in 0 length output. It may be a good
2384 const unsigned char *in, size_t inl)
2409 (unsigned char *)in, inl, out, &outl);
2417 (unsigned char *)in, inl, out, &outl);
2440 * here is the right thing because in EVP_DecryptFinal_ex(), engine's
2441 * do_cipher() is not even called, and in EVP_EncryptFinal_ex() it is called but
2458 * We are not interested in the data here, we just need to get
2485 * a particular NID in the ENGINE. This says what we'll do at the
2596 /* Create a secret key object in a PKCS#11 session */
2615 * Create secret key object in global_session. All other sessions
2624 * objects in a global session, an individual session may be closed to
2642 * Save the key information used in this session.
2711 /* 0 length message will cause a failure in C_DigestFinal */
2847 * that might have been allocated in the token when
2860 * Check if the new key is the same as the key object in the session. If the key
2899 * The secret key object is created in the