/frameworks/base/obex/javax/obex/ |
D | ObexSession.java | 81 byte[] challenge = ObexHelper.getTagValue((byte)0x00, header.mAuthChall); in handleAuthChall() 169 byte[] digest = new byte[challenge.length + password.length + 1]; in handleAuthChall() 170 System.arraycopy(challenge, 0, digest, 0, challenge.length); in handleAuthChall() 172 digest[challenge.length] = (byte)0x3A; in handleAuthChall() 173 System.arraycopy(password, 0, digest, challenge.length + 1, password.length); in handleAuthChall() 184 System.arraycopy(challenge, 0, header.mAuthResp, 20, 16); in handleAuthChall()
|
/frameworks/base/core/java/com/android/internal/widget/ |
D | LockPatternChecker.java | 52 final long challenge, in verifyPattern() argument 61 return utils.verifyPattern(pattern, challenge, userId); in verifyPattern() 122 final long challenge, in verifyPassword() argument 131 return utils.verifyPassword(password, challenge, userId); in verifyPassword() 159 final long challenge, in verifyTiedProfileChallenge() argument 168 return utils.verifyTiedProfileChallenge(password, isPattern, challenge, userId); in verifyTiedProfileChallenge()
|
D | ILockSettings.aidl | 33 VerifyCredentialResponse verifyPattern(in String pattern, long challenge, int userId); in verifyPattern() argument 36 VerifyCredentialResponse verifyPassword(in String password, long challenge, int userId); in verifyPassword() argument 37 …esponse verifyTiedProfileChallenge(String password, boolean isPattern, long challenge, int userId); in verifyTiedProfileChallenge() argument
|
D | LockPatternUtils.java | 313 public byte[] verifyPattern(List<LockPatternView.Cell> pattern, long challenge, int userId) in verifyPattern() argument 318 getLockSettings().verifyPattern(patternToString(pattern), challenge, userId); in verifyPattern() 370 public byte[] verifyPassword(String password, long challenge, int userId) in verifyPassword() argument 375 getLockSettings().verifyPassword(password, challenge, userId); in verifyPassword() 399 public byte[] verifyTiedProfileChallenge(String password, boolean isPattern, long challenge, in verifyTiedProfileChallenge() argument 404 getLockSettings().verifyTiedProfileChallenge(password, isPattern, challenge, in verifyTiedProfileChallenge()
|
/frameworks/base/services/core/java/com/android/server/ |
D | LockSettingsService.java | 1210 public VerifyCredentialResponse verifyPattern(String pattern, long challenge, int userId) in verifyPattern() argument 1212 return doVerifyPattern(pattern, true, challenge, userId); in verifyPattern() 1216 long challenge, int userId) throws RemoteException { in doVerifyPattern() argument 1219 return doVerifyPattern(pattern, storedHash, hasChallenge, challenge, userId); in doVerifyPattern() 1223 boolean hasChallenge, long challenge, int userId) throws RemoteException { in doVerifyPattern() argument 1234 hasChallenge, challenge, in doVerifyPattern() 1270 public VerifyCredentialResponse verifyPassword(String password, long challenge, int userId) in verifyPassword() argument 1272 return doVerifyPassword(password, true, challenge, userId); in verifyPassword() 1277 long challenge, int userId) throws RemoteException { in verifyTiedProfileChallenge() argument 1285 ? doVerifyPattern(password, true, challenge, parentProfileId) in verifyTiedProfileChallenge() [all …]
|
/frameworks/base/core/tests/coretests/src/android/net/http/ |
D | DefaultHttpClientTest.java | 126 String challenge = "Digest realm=\"protected area\", " in authenticateDigestAlgorithm() local 130 digestScheme.processChallenge(new BasicHeader("WWW-Authenticate", challenge)); in authenticateDigestAlgorithm()
|
/frameworks/base/docs/html/preview/features/ |
D | afw.jd | 14 <li><a href="#sec-challenge">Work Profile Security Challenge 98 <h2 id="sec-challenge">Work Profile Security Challenge</h2> 101 Profile owners can require users to specify a security challenge for apps 102 running in the work profile. The system shows the security challenge when the 104 security challenge, the system unlocks the work profile and decrypts it if 111 system prompts a user to set up a security challenge. The profile owner can 117 Profile owners can choose to set the password policies for the work challenge 119 minimum length for the device challenge response can be different from the 120 length required for other passwords. Profile owners set the challenge 130 the work challenge by using the {@link android.app.admin.DevicePolicyManager}
|
D | key-attestation.jd | 262 The challenge string associated with a key pair that is verified using key 685 The challenge string associated with the key pair that is defined in the
|
/frameworks/base/core/java/android/service/gatekeeper/ |
D | IGateKeeperService.aidl | 65 GateKeeperResponse verifyChallenge(int uid, long challenge, in byte[] enrolledPasswordHandle, in verifyChallenge() argument
|
/frameworks/base/docs/html-intl/intl/zh-cn/preview/features/ |
D | afw.jd | 18 <li><a href="#sec-challenge">工作资料安全性挑战</a> 102 <h2 id="sec-challenge">工作资料安全性挑战</h2>
|
/frameworks/base/docs/html-intl/intl/ja/preview/features/ |
D | afw.jd | 14 <li><a href="#sec-challenge">仕事用プロファイルによるセキュリティ確認</a> 98 <h2 id="sec-challenge">仕事用プロファイルによるセキュリティ確認</h2>
|
/frameworks/base/docs/html-intl/intl/ko/preview/features/ |
D | afw.jd | 14 <li><a href="#sec-challenge">작업 프로필 보안 인증 질문 98 <h2 id="sec-challenge">작업 프로필 보안 인증 질문</h2>
|
/frameworks/base/keystore/java/android/security/keystore/ |
D | AndroidKeyStoreKeyPairGeneratorSpi.java | 485 byte[] challenge = mSpec.getAttestationChallenge(); in createCertificateChain() 486 if (challenge != null) { in createCertificateChain() 488 args.addBytes(KeymasterDefs.KM_TAG_ATTESTATION_CHALLENGE, challenge); in createCertificateChain()
|
/frameworks/base/docs/html/preview/ |
D | api-overview.jd | 618 <h3 id="work_profile_security_challenge">Work profile security challenge </h3> 622 can specify a separate security challenge for apps running in 623 the work profile. The work challenge is shown when a user attempts to open 624 any work apps. Successful completion of the security challenge unlocks the 627 challenge, and <code>ACTION_SET_NEW_PARENT_PROFILE_PASSWORD</code> prompts 632 Profile owners can set distinct passcode policies for the work challenge 639 work challenge using the new <code>setOrganizationColor()</code> and
|
D | support.jd | 262 <li>After reboot with work mode off, solving work challenge does not switch 266 <li>Users receiving a video call in Hangouts have to unlock work challenge 271 separating primary and work challenge. 1276 <li>On a tablet, the background displayed with the work challenge is
|
/frameworks/base/docs/html/distribute/engage/ |
D | game-services.jd | 101 <strong>Multiplayer games:</strong> Add the challenge of playing against
|
/frameworks/base/docs/html-intl/intl/in/preview/features/ |
D | afw.jd | 14 <li><a href="#sec-challenge">Pertanyaan Keamanan Profil Kerja 98 <h2 id="sec-challenge">Pertanyaan Keamanan Profil Kerja</h2>
|
/frameworks/base/docs/html-intl/intl/pt-br/preview/features/ |
D | afw.jd | 14 <li><a href="#sec-challenge">Desafio de segurança de perfil de trabalho 98 <h2 id="sec-challenge">Desafio de segurança de perfil de trabalho</h2>
|
/frameworks/base/docs/html-intl/intl/es/preview/features/ |
D | afw.jd | 14 <li><a href="#sec-challenge">Comprobación de seguridad para perfiles de trabajo 98 <h2 id="sec-challenge">Comprobación de seguridad para perfiles de trabajo</h2>
|
/frameworks/opt/net/wifi/service/java/com/android/server/wifi/ |
D | WifiStateMachine.java | 7874 for (String challenge : requestData) { in getGsmSimAuthResponse() 7875 if (challenge == null || challenge.isEmpty()) { in getGsmSimAuthResponse() 7878 logd("RAND = " + challenge); in getGsmSimAuthResponse() 7882 rand = parseHex(challenge); in getGsmSimAuthResponse()
|
/frameworks/base/docs/html/guide/topics/media/ |
D | mediaplayer.jd | 466 multi-tasking environment. This poses a particular challenge to applications
|
/frameworks/base/docs/html/training/articles/ |
D | security-tips.jd | 250 <p>Each of these poses a significant non-technical challenge for you as the developer
|
/frameworks/base/docs/html/google/play/licensing/ |
D | adding-licensing.jd | 337 <p>At the same time, this {@code Policy} presents a challenge for normal users, since it
|