- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 86 for kms (0.59 sec)
-
internal/kms/kes.go
package kms import ( "bytes" "context" "crypto/subtle" "crypto/tls" "crypto/x509" "errors" "fmt" "strings" "sync" "time" "github.com/minio/pkg/v2/env" "github.com/minio/kms-go/kes" "github.com/minio/pkg/v2/certs" ) const ( tlsClientSessionCacheSize = 100 ) // Config contains various KMS-related configuration
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Apr 16 15:43:39 GMT 2024 - 14.9K bytes - Viewed (0) -
internal/crypto/metadata.go
MetaSealedKeyKMS = "X-Minio-Internal-Server-Side-Encryption-Kms-Sealed-Key" // MetaKeyID is the KMS master key ID used to generate/encrypt the data // encryption key (DEK). MetaKeyID = "X-Minio-Internal-Server-Side-Encryption-S3-Kms-Key-Id" // MetaDataEncryptionKey is the sealed data encryption key (DEK) received from // the KMS.
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 6.2K bytes - Viewed (0) -
docs/bucket/replication/delete-replication.sh
export MINIO_ROOT_USER="minio" export MINIO_ROOT_PASSWORD="minio123" export MINIO_KMS_AUTO_ENCRYPTION=off export MINIO_PROMETHEUS_AUTH_TYPE=public export MINIO_KMS_SECRET_KEY=my-minio-key:OSMM+vkKUTCvQs9YL/CVMIMt43HFhkUpqJxTmGl6rYw= unset MINIO_KMS_KES_CERT_FILE unset MINIO_KMS_KES_KEY_FILE unset MINIO_KMS_KES_ENDPOINT unset MINIO_KMS_KES_KEY_NAME if [ ! -f ./mc ]; then
Shell Script - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Mar 04 18:05:56 GMT 2024 - 2.9K bytes - Viewed (0) -
cmd/common-main.go
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat May 04 00:17:57 GMT 2024 - 35.8K bytes - Viewed (2) -
docs/bucket/versioning/versioning-tests.sh
} catch set -e export MINIO_CI_CD=1 export MINIO_BROWSER=off export MINIO_KMS_AUTO_ENCRYPTION=off export MINIO_PROMETHEUS_AUTH_TYPE=public export MINIO_KMS_SECRET_KEY=my-minio-key:OSMM+vkKUTCvQs9YL/CVMIMt43HFhkUpqJxTmGl6rYw= unset MINIO_KMS_KES_CERT_FILE unset MINIO_KMS_KES_KEY_FILE unset MINIO_KMS_KES_ENDPOINT unset MINIO_KMS_KES_KEY_NAME if [ ! -f ./mc ]; then
Shell Script - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 11 09:50:52 GMT 2024 - 2.4K bytes - Viewed (0) -
internal/kms/key-manager.go
package kms import ( "context" "github.com/minio/kms-go/kes" ) // KeyManager is the generic interface that handles KMS key operations type KeyManager interface { // CreateKey creates a new key at the KMS with the given key ID. CreateKey(ctx context.Context, keyID string) error // DeleteKey deletes a key at the KMS with the given key ID.
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Mar 01 21:09:42 GMT 2024 - 1.9K bytes - Viewed (0) -
internal/kms/policy-manager.go
// // You should have received a copy of the GNU Affero General Public License // along with this program. If not, see <http://www.gnu.org/licenses/>. package kms import ( "context" "github.com/minio/kms-go/kes" ) // PolicyManager is the generic interface that handles KMS policy] operations type PolicyManager interface { // DescribePolicy describes a policy by returning its metadata.
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Mar 01 21:09:42 GMT 2024 - 1.3K bytes - Viewed (0) -
.github/workflows/go.yml
- name: Build on ${{ matrix.os }} if: matrix.os == 'ubuntu-latest' env: CGO_ENABLED: 0 GO111MODULE: on MINIO_KMS_SECRET_KEY: "my-minio-key:OSMM+vkKUTCvQs9YL/CVMIMt43HFhkUpqJxTmGl6rYw=" MINIO_KMS_AUTO_ENCRYPTION: on run: | sudo sysctl net.ipv6.conf.all.disable_ipv6=0 sudo sysctl net.ipv6.conf.default.disable_ipv6=0
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Mar 28 23:44:49 GMT 2024 - 1.1K bytes - Viewed (0) -
cmd/encryption-v1.go
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 04 12:04:40 GMT 2024 - 36.5K bytes - Viewed (0) -
docs/site-replication/README.md
- All sites must be using the **same** external IDP(s) if any. - For [SSE-S3 or SSE-KMS encryption via KMS](https://min.io/docs/minio/linux/operations/server-side-encryption.html "MinIO KMS Guide"), all sites **must** have access to a central KMS deployment. This can be achieved via a central KES server or multiple KES servers (say one per site) connected via a central KMS (Vault) server. ## Configuring Site Replication
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Feb 26 21:30:28 GMT 2024 - 3.4K bytes - Viewed (0)