HomeSort by relevance Sort by last modified time
    Searched full:encrypt (Results 326 - 350 of 481) sorted by null

<<11121314151617181920

  /external/openssl/crypto/pkcs7/
pk7_smime.c 563 /* Encrypt BIOs can't do BIO_gets() so add a buffer BIO */
  /external/openssl/include/openssl/
des_old.h 414 # define ENCRYPT DES_ENCRYPT
ocsp.h 292 will (at least w/RSA) do a hash-'n'-private-encrypt operation. This seems
  /external/srtp/crypto/cipher/
aes_cbc.c 288 * now cbc encrypt the padded data
  /external/srtp/doc/
draft-irtf-cfrg-icm-00.txt 110 Crypto Forum Research Group David A. McGrew Internet Draft Cisco Systems, Inc. Expires April, 2003 October, 2002 Integer Counter Mode <draft-irtf-cfrg-icm-00.txt> Status of this Memo This document is an Internet Draft and is in full conformance with all provisions of Section 10 of RFC-2026. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and working groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. 1. Abstract This document specifies Integer Counter Mode (ICM), a mode of operation of a block cipher which defines an indexed keystream generator (which generates a keystream segment given an index). This mode is efficient, parallelizable, and has been proven secure given realistic assumptions about the block cipher. Test vectors are provided for AES. Counter Mode admits many variations. The variant specified in this document is secure and flexible, yet it enables a single implementation of a keystream generator to suffice in different application domains. McGrew [Page 1] Internet Draft Integer Counter Mode October, 2002 2. Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [B97]. 3. Introduction Counter Mode is a way to define a pseudorandom keystream generator using a block cipher [CTR]. The keystream can be used for additive encryption, key derivation, or any other application requiring pseudorandom data. In ICM, the keystream is logically broken into segments. Each segment is identified with a segment index, and the segments have equal lengths. This segmentation makes ICM especially appropriate for securing packet-based protocols. 4. ICM In this section, ICM keystream generation and encryption are defined. 4.1. ICM Parameters The following parameters are used in ICM. These parameters MUST remain fixed for any given use of a key. Parameter Meaning ----------------------------------------------------------------- BLOCK_LENGTH the number of octets in the cipher block KEY_LENGTH the number of octets in the cipher key OFFSET_LENGTH the number of octets in the offset SEGMENT_INDEX_LENGTH the number of octets in the segment index BLOCK_INDEX_LENGTH the number of octets in the block index 4.2. Keystream Segments Conceptually, ICM is a keystream generator that takes a secret key and a segment index as an input and then outputs a keystream segment. The segmentation lends itself to packet encryption, as each keystream segment can be used to encrypt a distinct packet. A counter is a value containing BLOCK_LENGTH octets which is McGrew (…)
  /external/webrtc/src/
common_types.h 153 virtual void encrypt(
  /external/wpa_supplicant_6/wpa_supplicant/src/crypto/
crypto_cryptoapi.c 727 wpa_printf(MSG_DEBUG, "CryptoAPI: Failed to encrypt using "
  /external/wpa_supplicant_6/wpa_supplicant/src/tls/
tlsv1_client.c 210 * tlsv1_client_encrypt - Encrypt data into TLS tunnel
tlsv1_server.c 184 * tlsv1_server_encrypt - Encrypt data into TLS tunnel
  /external/wpa_supplicant_8/src/ap/
ieee802_1x.c 45 int encrypt = 0; local
65 encrypt = 1;
70 encrypt, sta->flags);
159 wpa_printf(MSG_ERROR, "Could not encrypt key");
    [all...]
  /external/wpa_supplicant_8/src/crypto/
crypto_cryptoapi.c 718 wpa_printf(MSG_DEBUG, "CryptoAPI: Failed to encrypt using "
tls.h 375 * tls_connection_encrypt - Encrypt data into TLS tunnel
tls_nss.c 509 wpa_printf(MSG_DEBUG, "NSS: encrypt %d bytes",
  /external/wpa_supplicant_8/src/drivers/
driver_wired.c 310 const u8 *data, size_t data_len, int encrypt,
  /external/wpa_supplicant_8/src/tls/
tlsv1_server.c 189 * tlsv1_server_encrypt - Encrypt data into TLS tunnel
  /external/zlib/src/contrib/minizip/
minizip.c 184 because to encrypt a file, we need known the CRC32 of the file before */
zip.c 153 int encrypt; member in struct:__anon17195
    [all...]
  /frameworks/base/core/java/android/app/admin/
DevicePolicyManager.java     [all...]
  /frameworks/base/core/java/android/os/storage/
StorageManager.java 451 * @param key secret used to encrypt the OBB; may be <code>null</code> if no
  /frameworks/base/services/java/com/android/server/
DevicePolicyManagerService.java     [all...]
  /libcore/luni/src/main/java/javax/net/ssl/
SSLEngine.java 24 * protocols. It includes the setup, handshake, and encrypt/decrypt
  /libcore/luni/src/main/java/org/apache/harmony/xnet/provider/jsse/
ConnectionStateTLS.java 237 protected byte[] encrypt(byte type, byte[] fragment, int offset, int len) { method in class:ConnectionStateTLS
  /packages/apps/Email/emailcommon/src/com/android/emailcommon/provider/
Policy.java 410 sb.append("encrypt ");
  /system/vold/
DirectVolume.cpp 449 * Called from base to give cryptfs all the info it needs to encrypt eligible volumes
  /external/ipsec-tools/src/racoon/
eaytest.c 596 eay_func encrypt,
616 res1 = (encrypt)(buf, key, iv);

Completed in 623 milliseconds

<<11121314151617181920