/prebuilts/ndk/5/sources/cxx-stl/gnu-libstdc++/include/bits/ |
stl_queue.h | 119 * of private: to allow derivation. But none of the other 120 * containers allow for derivation. Odd.)
|
/prebuilts/ndk/6/sources/cxx-stl/gnu-libstdc++/include/bits/ |
stl_queue.h | 119 * of private: to allow derivation. But none of the other 120 * containers allow for derivation. Odd.)
|
/prebuilts/ndk/7/sources/cxx-stl/gnu-libstdc++/include/bits/ |
stl_queue.h | 119 * of private: to allow derivation. But none of the other 120 * containers allow for derivation. Odd.)
|
/prebuilts/ndk/8/sources/cxx-stl/gnu-libstdc++/4.4.3/include/bits/ |
stl_queue.h | 119 * of private: to allow derivation. But none of the other 120 * containers allow for derivation. Odd.)
|
/prebuilts/ndk/8/sources/cxx-stl/gnu-libstdc++/4.7/include/bits/ |
stl_queue.h | 122 * of private: to allow derivation. But none of the other 123 * containers allow for derivation. Odd.)
|
/prebuilts/ndk/9/sources/cxx-stl/gnu-libstdc++/4.7/include/bits/ |
stl_queue.h | 122 * of private: to allow derivation. But none of the other 123 * containers allow for derivation. Odd.)
|
/prebuilts/ndk/9/sources/cxx-stl/gnu-libstdc++/4.8/include/bits/ |
stl_queue.h | 123 * of private: to allow derivation. But none of the other 124 * containers allow for derivation. Odd.)
|
/external/srtp/srtp/ |
srtp.c | 285 * key derivation functions, internal to libSRTP 287 * srtp_kdf_t is a key derivation context 310 * srtp_kdf_t represents a key derivation function. The SRTP 315 aes_icm_ctx_t c; /* cipher used for key derivation */ 354 * end of key derivation functions [all...] |
/external/wpa_supplicant_8/hostapd/ |
ChangeLog | 52 * EAP-AKA': fixed identity for MK derivation 276 * fixed IEEE 802.11r key derivation function to match with the standard 278 * fixed SHA-256 based key derivation function to match with the 351 * added support for using SHA256-based stronger key derivation for WPA2 623 * fixed EAP-PAX CK and ICK key derivation [all...] |
/external/antlr/antlr-3.4/runtime/CSharp2/Sources/Antlr3.Runtime/Antlr.Runtime/ |
BaseRecognizer.cs | 530 * For input input "i=(3);", here is the derivation: 544 * as you can see by looking at the derivation of this specific 607 * derivation: [all...] |
/external/antlr/antlr-3.4/runtime/CSharp3/Sources/Antlr3.Runtime/ |
BaseRecognizer.cs | 601 * For input input "i=(3);", here is the derivation: 615 * as you can see by looking at the derivation of this specific 686 * derivation: [all...] |
/external/antlr/antlr-3.4/runtime/JavaScript/src/org/antlr/runtime/ |
BaseRecognizer.js | 553 * For input input "i=(3);", here is the derivation:</p> 569 * as you can see by looking at the derivation of this specific 635 * derivation:</p> [all...] |
/external/antlr/antlr-3.4/runtime/ObjC/Framework/ |
ANTLRBaseRecognizer.m | 640 * For input input "i=(3);", here is the derivation: 654 * as you can see by looking at the derivation of this specific 720 * derivation: [all...] |
/external/chromium/crypto/ |
symmetric_key_win.cc | 360 // CryptoAPI lacks routines to perform PBKDF2 derivation as specified
|
/external/chromium_org/crypto/ |
symmetric_key_win.cc | 360 // CryptoAPI lacks routines to perform PBKDF2 derivation as specified
|
/external/chromium_org/net/quic/crypto/ |
quic_crypto_server_config.h | 170 // guid: the GUID for the connection, which is used in key derivation.
|
/external/chromium_org/third_party/icu/source/common/ |
uprops.cpp | 595 // For the derivation, see Unicode's DerivedNormalizationProps.txt.
|
/external/chromium_org/third_party/mesa/src/src/glsl/ |
ast.h | 40 * direct representation of the gramma derivation for the source program.
|
/external/clang/include/clang/Basic/ |
DiagnosticASTKinds.td | 181 "%select{non-virtual|virtual}0 derivation here">;
|
/external/guava/guava/src/com/google/common/util/concurrent/ |
Futures.java | 182 * that the derivation runs in depends on whether the input {@code Future} is 184 * {@code chain} will run the derivation in the thread that called {@code 245 * caveats: First, the thread that the derivation runs in depends on whether 247 * particular, if called late, {@code chain} will run the derivation in the [all...] |
/external/icu4c/common/ |
uprops.cpp | 569 // For the derivation, see Unicode's DerivedNormalizationProps.txt.
|
/external/mesa3d/src/glsl/ |
ast.h | 40 * direct representation of the gramma derivation for the source program.
|
/external/openssh/ |
jpake.c | 347 /* Shared parts of key derivation and confirmation calculation */
|
/external/srtp/doc/ |
draft-irtf-cfrg-icm-00.txt | 76
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 bro (…)
|
/external/wpa_supplicant_8/src/eap_server/ |
eap_server_pax.c | 388 "key derivation");
|