- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 108 for trusted (0.03 sec)
-
okhttp/src/jvmTest/kotlin/okhttp3/internal/tls/CertificatePinnerChainValidationTest.kt
* * * The victim's gets a non-CA certificate signed by a CA, and pins the CA root and/or * intermediate. This is business as usual. * * ``` * pinnedRoot (trusted by CertificatePinner) * -> pinnedIntermediate (trusted by CertificatePinner) * -> realVictim * ``` * * The attacker compromises a CA. They take the public key from an intermediate certificate
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Fri Jun 20 11:46:46 UTC 2025 - 24.3K bytes - Viewed (2) -
src/main/java/jcifs/smb1/smb1/Dfs.java
/** * Cache of trusted domains for DFS resolution */ protected CacheEntry _domains = null; /* aka trusted domains cache */ /** * Cache of DFS referrals */ protected CacheEntry referrals = null; /** * Gets the map of trusted domains for DFS resolution * @param auth the authentication credentials * @return a map of trusted domain names to domain controllersRegistered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 14.2K bytes - Viewed (0) -
okhttp-tls/src/main/kotlin/okhttp3/tls/HeldCertificate.kt
* called certificate authorities (CAs). * * Browsers and other HTTP clients need a set of trusted root certificates to authenticate their * peers. Sets of root certificates are managed by either the HTTP client (like Firefox), or the * host platform (like Android). In July 2018 Android had 134 trusted root certificates for its HTTP * clients to trust. * * For example, in order to establish a secure connection to `https://www.squareup.com/`,
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 21.6K bytes - Viewed (0) -
src/main/java/jcifs/smb/NtStatus.java
/** The SAM database does not have a computer account for this workstation trust relationship */ int NT_STATUS_NO_TRUST_SAM_ACCOUNT = 0xC000018b; /** The trust relationship between the primary domain and the trusted domain failed */ int NT_STATUS_TRUSTED_DOMAIN_FAILURE = 0xC000018c; /** The trust relationship between this workstation and the primary domain failed */Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sun Aug 31 08:00:57 UTC 2025 - 14.9K bytes - Viewed (0) -
docs/features/https.md
Use [CertificatePinner](https://square.github.io/okhttp/4.x/okhttp/okhttp3/-certificate-pinner/) to restrict which certificates and certificate authorities are trusted. Certificate pinning increases security, but limits your server team’s abilities to update their TLS certificates. **Do not use certificate pinning without the blessing of your server’s TLS administrator!**
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Sat Dec 24 00:16:30 UTC 2022 - 10.5K bytes - Viewed (0) -
src/main/java/jcifs/smb1/smb1/NtStatus.java
int NT_STATUS_LOGON_TYPE_NOT_GRANTED = 0xC000015b; /** The SAM database does not have a computer account for this workstation trust relationship */ int NT_STATUS_NO_TRUST_SAM_ACCOUNT = 0xC000018b; /** The trust relationship between the primary domain and the trusted domain failed */ int NT_STATUS_TRUSTED_DOMAIN_FAILURE = 0xC000018c; /** The account used is a computer account */Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sun Aug 31 08:00:57 UTC 2025 - 13.2K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/CertificatePinner.kt
import okhttp3.internal.toCanonicalHost import okio.ByteString import okio.ByteString.Companion.decodeBase64 import okio.ByteString.Companion.toByteString /** * Constrains which certificates are trusted. Pinning certificates defends against attacks on * certificate authorities. It also prevents connections through man-in-the-middle certificate * authorities either known or unknown to the application's user.
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 14.1K bytes - Viewed (1) -
samples/guide/src/main/java/okhttp3/recipes/kt/WiresharkExample.kt
// Consuming ServerHello handshake message // Consuming server Certificate handshake message // Consuming server CertificateStatus handshake message // Found trusted certificate // Consuming ECDH ServerKeyExchange handshake message // Consuming ServerHelloDone handshake message // Produced ECDHE ClientKeyExchange handshake messageRegistered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Sat May 10 11:15:14 UTC 2025 - 10.9K bytes - Viewed (0) -
okhttp-testing-support/src/main/kotlin/okhttp3/OkHttpClientTestRule.kt
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Tue Nov 04 19:13:52 UTC 2025 - 10.8K bytes - Viewed (0) -
mockwebserver/src/main/kotlin/mockwebserver3/MockWebServer.kt
/** * Configure the server to [want client auth][SSLSocket.setWantClientAuth]. If the * client presents a certificate that is [trusted][TrustManager] the handshake will * proceed normally. The connection will also proceed normally if the client presents no * certificate at all! But if the client presents an untrusted certificate the handshake * will fail and no connection will be established. */ public fun requestClientAuth() {
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Sat Aug 02 20:36:00 UTC 2025 - 40.3K bytes - Viewed (0)