Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:failing (Results 501 - 525 of 1128) sorted by null

<<21222324252627282930>>

/external/chromium_org/ui/gl/
gl_surface_glx.cc	81 // since each failing call may spew an error message.
/external/chromium_org/webkit/browser/appcache/
appcache_url_request_job.cc	285 // Instead of failing the request, we restart the request. The retry
/external/clang/utils/
FuzzTest	180 '--no-revert'. Generally this is used with '--test <index>' to run one failing
/external/elfutils/libebl/
libebl.h	165 /* Check whether given symbol's st_value and st_size are OK despite failing
/external/elfutils/libelf/
libelf.h	404 /* Return error code of last failing function call. This value is kept
/external/icu4c/common/
resbund.cpp	34 * of failing UErrorCode values on entry to API methods.
/external/icu4c/i18n/unicode/
selfmt.h	279 * then it returns a failing UErrorCode.
/external/icu4c/test/cintltst/
hpmufn.c	359 log_info("Note: these failures may be caused by ICU failing to initialize/uninitialize properly.\n");
/external/icu4c/test/intltest/
tsputil.cpp	223 logln("and uses uprv_isNaN(). Therefore, most failing NaN tests only report warnings.");
/external/libffi/src/
closures.c	407 Failing that, fall back to dlmmap_locked. */
/external/llvm/bindings/python/llvm/
object.py	63 # In this example, we mix a working and failing scenario.
/external/llvm/lib/MC/
MCContext.cpp	397 // If we reached here, we are failing ungracefully. Run the interrupt handlers
/external/llvm/lib/Support/Unix/
Program.inc	393 // signal during execution as opposed to failing to execute.
/external/llvm/utils/lit/lit/
main.py	405 ('Failing Tests', lit.Test.FAIL)):
/external/openssh/
INSTALL	19 /dev/random, or failing that, either prngd or egd
/external/openssl/crypto/engine/
README	144 want to avoid every EVP_CIPHER_CTX setup from trying (and failing) to initialise
/external/qemu/distrib/sdl-1.2.15/src/video/x11/
SDL_x11yuv.c	47 /* Workaround intel i810 video overlay waiting with failing until the
/external/qemu/
qemu-sockets-android.c	505 * worst case possible is bind() failing, i.e. a DoS attack.
/external/skia/gm/rebaseline_server/
results.py	344 # ('tileimagefilter GM test failing in serialized render mode'),
/external/srtp/doc/
draft-irtf-cfrg-icm-00.txt	169 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 [Page 2] Internet Draft Integer Counter Mode October, 2002 incremented using an increment function based on integer addition, to produce a sequence of distinct values which are used as inputs to the block cipher. (In the context of this specification, an integer is an octet string, the most significant of which is the first.) The output blocks of the cipher are concatenated to form the keystream segment. The first octet of the segment is the first octet of the first output block, and so on. A schematic of this process is shown in Figure 1. Figure 1. The generation of a keystream segment given a segment index and a block cipher key K. Here C[i] and S[i] denote the ith counter and keystream block, respectively. segment index | v C[0] -----> C[1] -----> C[2] -----> ... | | | v v v +---+ +---+ +---+ K->| E | K->| E | K->| E | ... +---+ +---+ +---+ | | | v v v S[0] S[1] S[2] ... The ith counter C[i] of the keystream segment with segment index s is defined as C[i] = (i + s * (256^BLOCK_INDEX_LENGTH)) (+) r where r denotes the shifted Offset, which is defined as the Offset times 256^(BLOCK_LENGTH - OFFSET_LENGTH). (This multiplication left-shifts the Offset so that it is aligned with the leftmost edge of the block.) Here ^ denotes exponentiation and (+) denotes the bitwise exclusive-or operation. The number of blocks in any segment MUST NOT exceed 256^BLOCK_INDEX_LENGTH. The number of segments MUST NOT exceed 256^SEGMENT_INDEX_LENGTH. These restrictions ensure the uniqueness of each block cipher input. They also imply that each segment contains no more than (256^BLOCK_INDEX_LENGTH)*BLOCK_LENGTH octets. The sum of SEGMENT_INDEX_LENGTH and BLOCK_INDEX_LENGTH MUST NOT exceed BLOCK_LENGTH / 2. This requirement protects the ICM keystream generator from potentially failing to be pseudorandom (see McGrew [Page 3 (…)
/frameworks/base/core/java/android/app/admin/
DeviceAdminReceiver.java	145 * entered their password, after failing one or more times.
/frameworks/base/core/java/android/speech/tts/
TtsEngines.java	286 * value from {@link Settings.Secure#TTS_DEFAULT_LOCALE}, failing which the
/frameworks/base/core/java/android/util/
JsonWriter.java	412 * as newline characters. This prevents eval() from failing with a
/frameworks/base/core/java/com/android/internal/os/
RuntimeInit.java	185 * Converts various failing exceptions into RuntimeExceptions, with
/frameworks/base/core/tests/coretests/src/android/view/
FocusFinderTest.java	268 // failing test 4/10/2008, the values were tweaked somehow in functional

Completed in 1702 milliseconds

<<21222324252627282930>>