- Sort Score
- Result 10 results
- Languages All
Results 101 - 110 of 554 for secure (0.24 sec)
-
docs/tls/README.md
# How to secure access to MinIO server with TLS [](https://slack.min.io) This guide explains how to configure MinIO Server with TLS certificates on Linux and Windows platforms. 1. [Install MinIO Server](#install-minio-server) 2. [Use an Existing Key and Certificate with MinIO](#use-an-existing-key-and-certificate-with-minio)
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 8.6K bytes - Viewed (0) -
helm-releases/minio-1.0.2.tgz
displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 24 18:58:05 UTC 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-3.4.7.tgz
displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Jan 25 20:49:24 UTC 2022 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.2.0.tgz
displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed Oct 13 02:16:24 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.3.3.tgz
displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sat Dec 11 17:28:02 UTC 2021 - 14.6K bytes - Viewed (0) -
README.md
- **Crypto & Security** (`org.codelibs.core.crypto`, `org.codelibs.core.security`) - Basic cryptographic utilities, message digest operations, and secure random generation - **XML Processing** (`org.codelibs.core.xml`) - XML DOM utilities, SAX parser helpers, and schema validation support
Registered: Sat Dec 20 08:55:33 UTC 2025 - Last Modified: Sun Aug 31 02:56:02 UTC 2025 - 12.7K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/CertificatePinner.kt
* Peer certificate chain: * sha256/afwiKY3RxoMmLkuRW1l7QsPZTJPwDS2pdDROQjXw8ig=: CN=publicobject.com, OU=PositiveSSL * sha256/klO23nT2ehFDXCfx3eHTDRESMz3asj1muO+4aIdjiuY=: CN=COMODO RSA Secure Server CA * sha256/grX4Ta9HpZx6tSHkmCrvpApTQGo67CYDnvprLg5yRME=: CN=COMODO RSA Certification Authority * sha256/lCppFqbkrlJ3EcVFAkeip0+44VaoJUymbnOaEUk7tEU=: CN=AddTrust External CA Root
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 14.1K bytes - Viewed (1) -
docs/ko/docs/tutorial/extra-models.md
특히 사용자 모델의 경우에 그러한데, 왜냐하면: * **입력 모델** 은 비밀번호를 가져야 합니다. * **출력 모델** 은 비밀번호를 가지면 안됩니다. * **데이터베이스 모델** 은 해시처리된 비밀번호를 가질 것입니다. /// danger | 위험 절대 사용자의 비밀번호를 평문으로 저장하지 마세요. 항상 이후에 검증 가능한 "안전한 해시(secure hash)"로 저장하세요. 만약 이게 무엇인지 모르겠다면, [security chapters](security/simple-oauth2.md#password-hashing){.internal-link target=_blank}.에서 비밀번호 해시에 대해 배울 수 있습니다. /// ## 다중 모델Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Fri May 30 13:38:33 UTC 2025 - 8.4K bytes - Viewed (0) -
src/main/java/jcifs/config/BaseConfiguration.java
/** Local process ID for SMB messages */ protected int localPid = -1; /** Local timezone for time calculations */ protected TimeZone localTimeZone; /** Secure random generator for cryptographic operations */ protected SecureRandom random; /** Whether to use command batching for improved performance */ protected boolean useBatching = false;Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sun Aug 31 08:00:57 UTC 2025 - 36.5K bytes - Viewed (0) -
helm-releases/minio-3.1.2.tgz
displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sat Sep 18 04:26:47 UTC 2021 - 14.4K bytes - Viewed (0)