- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 183 for certificates (0.24 sec)
-
docs/en/docs/deployment/https.md
The domains are securely verified and the certificates are generated automatically. This also allows automating the renewal of these certificates.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jan 11 16:31:18 GMT 2024 - 12K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/CertificatePinner.kt
* `api.publicobject.com` are valid if either A's or B's certificate is in the chain. * * ## Warning: Certificate Pinning is Dangerous! * * Pinning certificates limits your server team's abilities to update their TLS certificates. By * pinning certificates, you take on additional operational complexity and limit your ability to * migrate between certificate authorities. Do not use certificate pinning without the blessing of
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 14.2K bytes - Viewed (1) -
okhttp-tls/src/main/kotlin/okhttp3/tls/HeldCertificate.kt
* certificate can sign other certificates (but those certificates cannot themselves sign * certificates). Set this to 1 so this certificate can sign intermediate certificates that can * themselves sign certificates. Add one for each additional layer of intermediates to permit. */ fun certificateAuthority(maxIntermediateCas: Int) = apply {
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 21.6K bytes - Viewed (1) -
docs/features/https.md
on-300-000-iranians-using-fake-google-certificate.html). It also assumes your HTTPS servers’ certificates are signed by a certificate authority. 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...
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Sat Dec 24 00:16:30 GMT 2022 - 10.5K bytes - Viewed (0) -
common-protos/k8s.io/api/certificates/v1/generated.proto
// 5. Expiration/certificate lifetime: whether it is fixed by the signer, configurable by the admin. // 6. Whether or not requests for CA certificates are allowed. optional string signerName = 7; // expirationSeconds is the requested duration of validity of the issued // certificate. The certificate signer may issue a certificate with a different
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 11.6K bytes - Viewed (0) -
helm/minio/README.md
``` ### Installing certificates from third party CAs
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Jan 24 07:27:57 GMT 2024 - 10.9K bytes - Viewed (0) -
docs/changelogs/changelog_4x.md
``` Get these strings with `HeldCertificate.certificatePem()` and `privateKeyPkcs8Pem()`. * Fix: Handshake now returns peer certificates in canonical order: each certificate is signed by the certificate that follows and the last certificate is signed by a trusted root. * Fix: Don't lose HTTP/2 flow control bytes when incoming data races with a stream close. If this
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Wed Apr 17 13:25:31 GMT 2024 - 25.2K bytes - Viewed (0) -
architecture/ambient/ztunnel.md
## Certificates Ztunnel certificates are based on the standard Istio SPIFFE format: `spiffe://<trust domain>/ns/<ns>/sa/<sa>`. However, the identities of the certificates will be of the actual user workloads, not Ztunnel's own identity. This means Ztunnel will have multiple distinct certificates at a time, one for each unique identity (service account) running on its node.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 25 22:35:16 GMT 2024 - 16.6K bytes - Viewed (0) -
okhttp/src/test/java/okhttp3/internal/tls/CertificatePinnerChainValidationTest.kt
// Add a bad intermediate CA and have that issue a rogue certificate for localhost. Prepare // an SSL context for an attacking webserver. It includes both these rogue certificates plus the // trusted good certificate above. The attack is that by including the good certificate in the // chain, we may trick the certificate pinner into accepting the rouge certificate. val compromisedIntermediateCa = HeldCertificate.Builder()
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 23.8K bytes - Viewed (0) -
istioctl/pkg/ztunnelconfig/ztunnelconfig.go
common := new(commonFlags) cmd := &cobra.Command{ Use: "certificate", Short: "Retrieves certificate for the specified Ztunnel pod.", Long: `Retrieve information about certificates for the Ztunnel instance.`, Example: ` # Retrieve summary about workload configuration for a randomly chosen ztunnel. istioctl x ztunnel-config certificates # Retrieve full certificate dump of workloads for a given Ztunnel instance.
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed May 01 13:11:40 GMT 2024 - 22.2K bytes - Viewed (0)