- Sort Score
- Result 10 results
- Languages All
Results 101 - 110 of 130 for crt (0.03 sec)
-
docs/distributed/decom-encrypted-kes.sh
API_KEY=$(grep "API Key" <kes-server.log | awk -F" " '{print $3}') (openssl s_client -connect 127.0.0.1:7373 2>/dev/null 1>public.crt) export CI=true export MINIO_KMS_KES_ENDPOINT=https://127.0.0.1:7373 export MINIO_KMS_KES_API_KEY="${API_KEY}" export MINIO_KMS_KES_KEY_NAME=minio-default-key export MINIO_KMS_KES_CAPATH=public.crt export MC_HOST_myminio="http://minioadmin:minioadmin@localhost:9000/"
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon May 27 19:17:46 UTC 2024 - 7.1K bytes - Viewed (0) -
docs/site-replication/run-ssec-object-replication-with-compression.sh
echo -n "Setup certs for MinIO instances ..." wget -O certgen https://github.com/minio/certgen/releases/latest/download/certgen-linux-amd64 && chmod +x certgen ./certgen --host localhost mkdir -p /tmp/certs mv public.crt /tmp/certs || sudo mv public.crt /tmp/certs mv private.key /tmp/certs || sudo mv private.key /tmp/certs echo "done" # Start MinIO instances echo -n "Starting MinIO instances ..."
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Sep 24 08:03:58 UTC 2024 - 8.3K bytes - Viewed (0) -
helm-releases/minio-5.1.0.tgz
third party CAs, remember to include MinIO's own certificate with key `public.crt`, if it also needs to be trusted. For instance, given that TLS is enabled and you need to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Mar 03 18:49:37 UTC 2024 - 21.3K bytes - Viewed (0) -
helm-releases/minio-5.2.0.tgz
third party CAs, remember to include MinIO's own certificate with key `public.crt`, if it also needs to be trusted. For instance, given that TLS is enabled and you need to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Apr 28 10:14:37 UTC 2024 - 21.7K bytes - Viewed (0) -
cmd/config-dir.go
certsDir = "certs" // Directory contains all CA certificates other than system defaults for HTTPS. certsCADir = "CAs" // Public certificate file for HTTPS. publicCertFile = "public.crt" // Private key file for HTTPS. privateKeyFile = "private.key" ) // ConfigDir - points to a user set directory. type ConfigDir struct { path string } func getDefaultConfigDir() string {
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Jan 02 17:15:06 UTC 2022 - 3K bytes - Viewed (0) -
Dockerfile.release
MINIO_CONFIG_ENV_FILE=config.env \ MC_CONFIG_DIR=/tmp/.mc RUN chmod -R 777 /usr/bin COPY --from=build /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ COPY --from=build /go/bin/minio* /usr/bin/ COPY --from=build /go/bin/mc* /usr/bin/ COPY --from=build /go/bin/curl* /usr/bin/ COPY CREDITS /licenses/CREDITS COPY LICENSE /licenses/LICENSE
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Sep 15 23:10:23 UTC 2024 - 3K bytes - Viewed (0) -
Dockerfile.release.old_cpu
MINIO_CONFIG_ENV_FILE=config.env \ MC_CONFIG_DIR=/tmp/.mc RUN chmod -R 777 /usr/bin COPY --from=build /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ COPY --from=build /go/bin/minio* /usr/bin/ COPY --from=build /go/bin/mc* /usr/bin/ COPY --from=build /go/bin/cur* /usr/bin/ COPY CREDITS /licenses/CREDITS COPY LICENSE /licenses/LICENSE
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Sep 15 23:10:23 UTC 2024 - 3.1K bytes - Viewed (0) -
docs/sts/etcd.md
minio server /data ``` NOTE: If `etcd` is configured with `Client-to-server authentication with HTTPS client certificates` then you need to use additional envs such as `MINIO_ETCD_CLIENT_CERT` pointing to path to `etcd-client.crt` and `MINIO_ETCD_CLIENT_CERT_KEY` path to `etcd-client.key` . ### 4. Test with MinIO STS API Once etcd is configured, **any STS configuration** will work including Client Grants, Web Identity or AD/LDAP.
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 29 04:28:45 UTC 2022 - 3.4K bytes - Viewed (0) -
cmd/ftp-server.go
} if tlsPrivateKey != "" && tlsPublicCert == "" { logger.Fatal(fmt.Errorf("invalid TLS arguments provided missing public cert --ftp=\"tls-public-cert=path/to/public.crt\""), "unable to start FTP server") } if port == 0 { port = 8021 // Default FTP port, since no port was given. } } // If no TLS certs were provided, server is running in TLS for S3 API
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Mar 09 03:07:08 UTC 2024 - 4.8K bytes - Viewed (0) -
helm-releases/minio-5.0.11.tgz
third party CAs, remember to include MinIO's own certificate with key `public.crt`, if it also needs to be trusted. For instance, given that TLS is enabled and you need to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Jun 21 19:29:09 UTC 2023 - 20.3K bytes - Viewed (0)