- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 49 for Trusted (0.04 sec)
-
okhttp/src/jvmTest/kotlin/okhttp3/CertificateChainCleanerTest.kt
selfSigned.certificate, trusted.certificate, ) assertThat(cleaner.clean(list(certB, certA), "hostname")).isEqualTo( list(certB, certA, trusted, selfSigned), ) assertThat(cleaner.clean(list(certB, certA, trusted), "hostname")).isEqualTo( list(certB, certA, trusted, selfSigned), ) assertThat(cleaner.clean(list(certB, certA, trusted, selfSigned), "hostname")) .isEqualTo(
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 9.5K bytes - Viewed (1) -
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 Sep 05 11:42:10 UTC 2025 - Last Modified: Fri Jun 20 11:46:46 UTC 2025 - 24.3K bytes - Viewed (1) -
okhttp-tls/src/main/kotlin/okhttp3/tls/HandshakeCertificates.kt
/** * Configure the certificate chain to use when being authenticated. The first certificate is * the held certificate, further certificates are included in the handshake so the peer can * build a trusted path to a trusted root certificate. * * The chain should include all intermediate certificates but does not need the root certificate * that we expect to be known by the remote peer. The peer already has that certificate so
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Sat May 10 11:15:14 UTC 2025 - 8.4K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/tls/CertificateChainCleaner.kt
* certificate is signed by the certificate that follows, and the last certificate is a trusted CA * certificate. * * Use of the chain cleaner is necessary to omit unexpected certificates that aren't relevant to * the TLS handshake and to extract the trusted CA certificate for the benefit of certificate * pinning. */ abstract class CertificateChainCleaner {
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 2K bytes - Viewed (0) -
src/main/java/jcifs/DfsResolver.java
* * <p>This interface is intended for internal use.</p> */ public interface DfsResolver { /** * Checks if a domain is trusted for DFS operations * @param tf the CIFS context * @param domain the domain name to check * @return whether the given domain is trusted * @throws CIFSException if the operation fails */ boolean isTrustedDomain(CIFSContext tf, String domain) throws CIFSException;
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 2.4K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/tls/BasicCertificateChainCleaner.kt
val toVerify = result[result.size - 1] as X509Certificate // If this cert has been signed by a trusted cert, use that. Add the trusted certificate to // the end of the chain unless it's already present. (That would happen if the first // certificate in the chain is itself a self-signed and trusted CA certificate.) val trustedCert = trustRootIndex.findByIssuerAndSignature(toVerify) if (trustedCert != null) {
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 4.8K bytes - Viewed (0) -
okhttp-tls/README.md
----------------------- The above example uses a self-signed certificate. This is convenient for testing but not representative of real-world HTTPS deployment. To get closer to that we can use `HeldCertificate` to generate a trusted root certificate, an intermediate certificate, and a server certificate. We use `certificateAuthority(int)` to create certificates that can sign other certificates. The
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Mon Jul 07 19:32:33 UTC 2025 - 9.1K bytes - Viewed (0) -
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 controllers
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 14.2K bytes - Viewed (0) -
cmd/sftp-server.go
if err != nil { logger.Fatal(fmt.Errorf("invalid arguments passed, trusted user certificate authority public key file is not accessible: %v", err), "unable to start SFTP server") } globalSFTPTrustedCAPubkey, _, _, _, err = ssh.ParseAuthorizedKey(keyBytes) if err != nil {
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 29 02:39:48 UTC 2025 - 16.5K bytes - Viewed (0) -
docs/ftp/README.md
******@****.*** ******@****.*** hmac-sha2-256 hmac-sha2-512 hmac-sha1 hmac-sha1-96 ``` ### Certificate-based authentication `--sftp=trusted-user-ca-key=...` specifies a file containing public key of certificate authority that is trusted to sign user certificates for authentication. Implementation is identical with "TrustedUserCAKeys" setting in OpenSSH server with exception that only one CA
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue May 07 06:41:25 UTC 2024 - 7.8K bytes - Viewed (0)