| /external/tcpdump/tests/ |
| D | bfd-raw-auth-md5.out | 1 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
2 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
3 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
4 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
5 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
6 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
7 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
8 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
9 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
10 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
[all …]
|
| D | bfd-raw-auth-sha1.out | 1 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
2 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
3 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
4 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
5 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
6 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
7 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
8 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
9 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
10 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
[all …]
|
| D | bfd-raw-auth-md5-v.out | 3 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
9 Authentication: Keyed MD5 (2), length: 24
14 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
20 Authentication: Keyed MD5 (2), length: 24
25 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
31 Authentication: Keyed MD5 (2), length: 24
36 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
42 Authentication: Keyed MD5 (2), length: 24
47 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
53 Authentication: Keyed MD5 (2), length: 24
[all …]
|
| D | bfd-raw-auth-sha1-v.out | 3 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
9 Authentication: Meticulous Keyed SHA1 (5), length: 28
14 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
20 Authentication: Meticulous Keyed SHA1 (5), length: 28
25 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
31 Authentication: Meticulous Keyed SHA1 (5), length: 28
36 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
42 Authentication: Meticulous Keyed SHA1 (5), length: 28
47 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
53 Authentication: Meticulous Keyed SHA1 (5), length: 28
[all …]
|
| D | bfd-raw-auth-simple-v.out | 3 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
9 Authentication: Simple Password (1), length: 9
13 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
19 Authentication: Simple Password (1), length: 9
23 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
29 Authentication: Simple Password (1), length: 9
33 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
39 Authentication: Simple Password (1), length: 9
43 Control, State Down, Flags: [Authentication Present], Diagnostic: No Diagnostic (0x00)
49 Authentication: Simple Password (1), length: 9
[all …]
|
| D | bfd-raw-auth-simple.out | 1 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
2 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
3 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
4 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
5 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
6 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
7 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
8 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
9 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
10 …92.85.1.2.1024 > 192.0.0.1.3784: BFDv1, Control, State Down, Flags: [Authentication Present], leng…
[all …]
|
| /external/obex/src/com/android/obex/ |
| D | Authenticator.java | 36 * This interface provides a way to respond to authentication challenge and
37 * authentication response headers. When a client or server receives an
38 * authentication challenge or authentication response header, the
43 * For more information on how the authentication procedure works in OBEX,
47 * <STRONG>Authentication Challenges</STRONG>
49 * When a client or server receives an authentication challenge header, the
53 * password in this object is not sent in the authentication response. Instead,
54 * the 16-byte challenge received in the authentication challenge is combined
57 * in the authentication response along with the user name if it was provided.
59 * <STRONG>Authentication Responses</STRONG>
[all …]
|
| /external/wpa_supplicant_8/hostapd/ |
| D | README | 2 Authenticator and RADIUS authentication server
56 included in the kernel driver: using external RADIUS authentication
62 EAP server (i.e., allow full authentication without requiring
63 an external RADIUS authentication server), and RADIUS authentication
64 server for EAP authentication.
81 Any wired Ethernet driver for wired IEEE 802.1X authentication
104 minimal authentication mechanism for stations, whereas IEEE 802.1X
109 Access Entity, and Authentication Server. Supplicant is a component in
110 a station and it performs the authentication with the Authentication
112 between a Supplicant and an Authentication Server. In addition, it has a
[all …]
|
| /external/curl/docs/libcurl/opts/ |
| D | CURLOPT_HTTPAUTH.3 | 27 CURLOPT_HTTPAUTH \- HTTP server authentication methods to try
35 authentication method(s) you want it to use speaking to the remote server.
38 first query the site to see which authentication methods it supports and then
44 For authentication with a proxy, see \fICURLOPT_PROXYAUTH(3)\fP.
47 HTTP Basic authentication. This is the default choice, and the only method
52 HTTP Digest authentication. Digest authentication is defined in RFC2617 and
53 is a more secure way to do authentication over public networks than the
56 HTTP Digest authentication with an IE flavor. Digest authentication is
57 defined in RFC2617 and is a more secure way to do authentication over public
62 HTTP Bearer token authentication, used primarily in OAuth 2.0 protocol.
[all …]
|
| /external/cronet/net/http/ |
| D | http_auth_controller.h | 39 // authentication stack. A single instance of an HttpAuthController can be used
40 // to handle authentication to a single "target", where "target" is a HTTP
42 // of multiple authentication handlers (implemented as HttpAuthHandler
45 // Individual HTTP authentication schemes can have additional requirements other
52 // * |target| is either PROXY or SERVER and determines the authentication
59 // 3.3) of the URL is used by HTTP basic authentication to determine
70 // authentication if explicit (user-provided) credentials are used and
71 // they can be cached to respond to authentication challenges in the
73 // authentication is stateful across requests. So the |http_auth_cache|
74 // is also used to maintain state for this authentication scheme.
[all …]
|
| D | http_auth_handler.h | 23 // HttpAuthHandler is the interface for the authentication schemes
31 // For connection-based authentication, an HttpAuthHandler handles all rounds
46 // authentication scheme, but none of the tokens occurring after the
47 // authentication scheme.
68 // is required. For Digest authentication it may also mean that the previous
73 // authentication scheme, but none of the tokens occurring after the
74 // authentication scheme.
78 // Generates an authentication token, potentially asynchronously.
88 // If |OK| is returned, |*auth_token| is filled in with an authentication
103 // The authentication scheme as an enumerated value.
[all …]
|
| D | http_auth.h | 32 // Utility class for http authentication.
35 // Http authentication can be done to the proxy server, origin server,
59 AUTHORIZATION_RESULT_INVALID, // The authentication challenge headers are
71 // Describes where the identity used for authentication came from.
112 // authentication.
145 // Returns a string representation of an authentication Scheme.
148 // Returns an authentication Scheme from a string which was produced by
168 // |scheme_host_port| is used by the NTLM and Negotiation authentication
172 // |ssl_info| is passed through to the scheme specific authentication handlers
187 // authentication attempt. For connection-based authentication schemes, the
[all …]
|
| D | http_auth_handler_factory.h | 55 // Sets the source of the HTTP authentication preferences.
69 // Creates an HttpAuthHandler object based on the authentication challenge
75 // If |*challenge| specifies an unsupported authentication scheme, |*handler|
84 // |digest_nonce_count| is specifically intended for the Digest authentication
88 // |ssl_info| is valid if the authentication session is being established over
92 // If |origin| does not match the authentication method's filters for
98 // |host_resolver| is used by the Negotiate authentication handler to perform
115 // Creates an HTTP authentication handler based on the authentication
130 // Creates an HTTP authentication handler based on the authentication
150 // used by the Negotiate authentication handler.
[all …]
|
| /external/python/google-api-python-client/docs/dyn/ |
| D | websecurityscanner_v1.projects.scanConfigs.html | 122 …ot;authentication": { # Scan authentication configuration. # The authentication configuration…
123 …quot;customAccount": { # Describes authentication configuration that uses a custom account. #…
128 …quot;googleAccount": { # Describes authentication configuration that uses a Google account. #…
132 …ot;iapCredential": { # Describes authentication configuration for Identity-Aware-Proxy (IAP).…
133 …ibes authentication configuration when Web-Security-Scanner service account is added in Identity-A…
168 …ot;authentication": { # Scan authentication configuration. # The authentication configuration…
169 …quot;customAccount": { # Describes authentication configuration that uses a custom account. #…
174 …quot;googleAccount": { # Describes authentication configuration that uses a Google account. #…
178 …ot;iapCredential": { # Describes authentication configuration for Identity-Aware-Proxy (IAP).…
179 …ibes authentication configuration when Web-Security-Scanner service account is added in Identity-A…
[all …]
|
| /external/apache-http/src/org/apache/http/auth/ |
| D | AuthScheme.java | 39 * authentication scheme.
42 * An authentication scheme should be able to support the following
49 * <li>Provide the realm this authentication scheme is applicable to,
57 * Authentication schemes may ignore method name and URI parameters
58 * if they are not relevant for the given authentication mechanism
61 * Authentication schemes may be stateful involving a series of
79 * Processes the given challenge token. Some authentication schemes
88 * Returns textual designation of the given authentication scheme.
90 * @return the name of the given authentication scheme
95 * Returns authentication parameter with the given name, if available.
[all …]
|
| D | AuthSchemeRegistry.java | 42 * Authentication scheme registry that can be used to obtain the corresponding
43 * authentication scheme implementation for a given type of authorization challenge.
68 * retrieve the {@link AuthScheme authentication scheme} from {@link #getAuthScheme}.
71 * Please note that custom authentication preferences, if used, need to be updated accordingly
72 * for the new {@link AuthScheme authentication scheme} to take effect.
87 throw new IllegalArgumentException("Authentication scheme factory may not be null"); in register()
93 * Unregisters the class implementing an {@link AuthScheme authentication scheme} with
106 * Gets the {@link AuthScheme authentication scheme} with the given name.
108 * @param name the {@link AuthScheme authentication scheme} identifier
109 * @param params the {@link HttpParams HTTP parameters} for the authentication
[all …]
|
| D | AuthState.java | 36 * authentication process.
49 /** Actual authentication scheme */
52 /** Actual authentication scope */
55 /** Credentials selected for authentication */
67 * Invalidates the authentication state by resetting its parameters.
80 * Assigns the given {@link AuthScheme authentication scheme}.
82 * @param authScheme the {@link AuthScheme authentication scheme}
93 * Returns the {@link AuthScheme authentication scheme}.
95 * @return {@link AuthScheme authentication scheme}
103 * Returns user {@link Credentials} selected for authentication if available
[all …]
|
| /external/exoplayer/tree_15dc86382f17a24a3e881e52e31a810c1ea44b49/library/rtsp/src/main/java/com/google/android/exoplayer2/source/rtsp/ |
| D | RtspAuthenticationInfo.java | 29 /** Wraps RTSP authentication information. */
32 /** The supported authentication methods. */
37 /** HTTP basic authentication (RFC2068 Section 11.1). */
39 /** HTTP digest authentication (RFC2069). */
50 /** The authentication mechanism. */
52 /** The authentication realm. */
54 /** The nonce used in digest authentication; empty if using {@link #BASIC} authentication. */
56 /** The opaque used in digest authentication; empty if using {@link #BASIC} authentication. */
62 * @param authenticationMechanism The authentication mechanism, as defined by {@link
64 * @param realm The authentication realm.
[all …]
|
| /external/exoplayer/tree_8e57d3715f9092d5ec54ebe2e538f34bfcc34479/library/rtsp/src/main/java/com/google/android/exoplayer2/source/rtsp/ |
| D | RtspAuthenticationInfo.java | 33 /** Wraps RTSP authentication information. */
36 /** The supported authentication methods. */
43 /** HTTP basic authentication (RFC2068 Section 11.1). */
45 /** HTTP digest authentication (RFC2069). */
56 /** The authentication mechanism. */
58 /** The authentication realm. */
60 /** The nonce used in digest authentication; empty if using {@link #BASIC} authentication. */
62 /** The opaque used in digest authentication; empty if using {@link #BASIC} authentication. */
68 * @param authenticationMechanism The authentication mechanism, as defined by {@link
70 * @param realm The authentication realm.
[all …]
|
| /external/arm-trusted-firmware/docs/design/ |
| D | auth-framework.rst | 1 Authentication Framework & Chain of Trust
4 The aim of this document is to describe the authentication framework
62 This document describes the inner details of the authentication framework and
74 A CoT is basically a sequence of authentication images which usually starts with
125 Images in a CoT are categorised as authentication and data images. An
126 authentication image contains information to authenticate a data image or
127 another authentication image. A data image is usually a boot loader binary, but
128 it could be any other data that requires authentication.
144 #. If the image is an authentication image, extract the information that will
153 These components are responsible for initiating the authentication process for a
[all …]
|
| /external/grpc-grpc/doc/ |
| D | server_side_auth.md | 4 …ibes how server-side authentication works in C-core based gRPC implementations only. In gRPC Java …
8 …authentication, gRPC exposes the *authentication context* for each call. The context exposes impor…
10 The authentication context is structured as a multi-map of key-value pairs - the *auth properties*.…
12 …perty key will act as the peer identity (e.g. for client certificate authentication this property …
14 … to authenticating RPCs. Using any other call/context properties for authentication purposes is wr…
18 For secure channel using mutual TLS authentication with both client and server certificates (test c…
49 - TLS/SSL certificate authentication (built into gRPC's security layer, automatically used whenever…
50 - (coming soon) JWT auth token authentication
|
| /external/arm-trusted-firmware/include/drivers/auth/ |
| D | auth_common.h | 11 * Authentication framework common types
16 * used for authentication
29 * Defines an authentication parameter. The cookie will be interpreted by the
38 * Store a pointer to the authentication parameter and its length
46 * Authentication parameter descriptor, including type and value
65 * Parameters for authentication by hash matching
73 * Parameters for authentication by signature
83 * Parameters for authentication by NV counter
91 * Authentication method descriptor
103 * Helper macro to define an authentication parameter type descriptor
[all …]
|
| /external/python/google-auth-library-python/google/oauth2/ |
| D | utils.py | 19 `Client authentication for OAuth flows`_.
29 Client authentication for OAuth flows
31 We introduce an interface for defining client authentication credentials based
35 * Ability to support basic authentication via request header.
36 * Ability to support bearer token authentication via request header.
37 * Ability to support client ID / secret authentication via request body.
53 # OAuth client authentication based on
61 """Defines the client authentication credentials for basic and request-body
66 """Instantiates a client authentication object containing the client ID
71 client authentication type.
[all …]
|
| /external/wpa_supplicant_8/hs20/server/www/ |
| D | spp.php | 43 error_log("spp.php - Authentication failed - missing: " . print_r($needed));
44 die('Authentication failed');
48 error_log("spp.php - Authentication failed - empty username");
49 die('Authentication failed');
67 error_log("spp.php - Authentication failed - user '$user' not found");
68 die('Authentication failed');
71 error_log("spp.php - Authentication failed - empty password");
72 die('Authentication failed');
80 error_log("Authentication failure - response mismatch");
81 die('Authentication failed');
[all …]
|
| /external/apache-http/android/src/android/net/http/ |
| D | HttpAuthHeader.java | 22 * HttpAuthHeader: a class to store HTTP authentication-header parameters.
23 * For more information, see: RFC 2617: HTTP Authentication.
27 * Possible HTTP-authentication header tokens to search for:
40 * An authentication scheme. We currently support two different schemes:
84 * value "auth" indicates authentication; the value "auth-int"
85 * indicates authentication with integrity protection.
96 * Is this authentication request a proxy authentication request?
111 * Creates a new HTTP-authentication header object from the
114 * most one authentication-scheme (ensured by the caller).
123 * @return True iff this is a proxy authentication header.
[all …]
|