- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 201 for trusted (0.05 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 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
/** * Certificates to identify which peers to trust and also to earn the trust of those peers in kind. * Client and server exchange these certificates during the handshake phase of a TLS connection. * * ### Server Authentication * * This is the most common form of TLS authentication: clients verify that servers are trusted and * that they own the hostnames that they represent. Server authentication is required.
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-tls/README.md
``` This handshake is successful because each party has prearranged to trust the root certificate that signs the other party's chain. Well-Known Certificate Authorities ---------------------------------- In these examples we've prearranged which root certificates to trust. But for regular HTTPS on the Internet this set of trusted root certificates is usually provided by default by the host platform.
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/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) -
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/en/docs/deployment/https.md
/// Nevertheless, as the **application server** doesn't know it is behind a trusted **proxy**, by default, it wouldn't trust those headers. But you can configure the **application server** to trust the *forwarded* headers sent by the **proxy**. If you are using FastAPI CLI, you can use the *CLI Option* `--forwarded-allow-ips` to tell it from which IPs it should trust those *forwarded* headers.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 19:34:08 UTC 2025 - 14.3K 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: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sun Aug 31 08:00:57 UTC 2025 - 14.9K 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: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sun Aug 31 08:00:57 UTC 2025 - 13.2K bytes - Viewed (0) -
docs/en/docs/advanced/behind-a-proxy.md
You can start FastAPI CLI with the *CLI Option* `--forwarded-allow-ips` and pass the IP addresses that should be trusted to read those forwarded headers. If you set it to `--forwarded-allow-ips="*"` it would trust all the incoming IPs. If your **server** is behind a trusted **proxy** and only the proxy talks to it, this would make it accept whatever is the IP of that **proxy**. <div class="termy"> ```console
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 19:34:08 UTC 2025 - 16K bytes - Viewed (0)