关于“Using Customer-Managed Encryption Keys with Cloud Storage and Cloud KMS”的评价
评论
Atul J. · 评论over 3 years之前
Matthew C. · 评论over 3 years之前
Rajesh N. · 评论over 3 years之前
Eddie B. · 评论over 3 years之前
Stephane H. · 评论over 3 years之前
Benoit B. · 评论over 3 years之前
julien T. · 评论over 3 years之前
Maria N. · 评论over 3 years之前
Another great hands on practice!
Majed A. · 评论over 3 years之前
Justin C. · 评论over 3 years之前
Reinhard S. · 评论over 3 years之前
Benson G. · 评论over 3 years之前
Brandon K. · 评论over 3 years之前
Jesus O. · 评论over 3 years之前
ananth v. · 评论over 3 years之前
Alejandro B. · 评论over 3 years之前
Unmesh T. · 评论over 3 years之前
Ankit S. · 评论over 3 years之前
there were two syntax issues in the instructions 1) Set the default key for a bucket wrong syntax: gsutil kms encryption -k \ projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings\ /$KEYRIN correct syntax: gsutil kms encryption -k projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings/$KEYRING_NAME/cryptoKeys/$CRYPTOKEY_1_NAME gs://$DEVSHELL_PROJECT_ID-kms 2) Bonus: Encrypt data with the REST API Step 8 command wrong syntax: curl -v \ "https://cloudkms.googleapis.com/v1/projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings/$KEYRING_NAME/cryptoKeys/$CRYPTOKEY_1_NAME:decrypt" \ -d "{\"ciphertext\":\"$(cat data1.encrypted)\"}" \ -H "Authorization:Be Correct syntax: curl -v \ "https://cloudkms.googleapis.com/v1/projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings/$KEYRING_NAME/cryptoKeys/$CRYPTOKEY_1_NAME:decrypt" \ -d "{\"ciphertext\":\"$(cat data1.encrypted)\"}" \ -H "Authorization:Bearer $(gcloud auth application-default \ print-access-token)" \ -H "Content-Type: application/json" \ | jq .plaintext -r > data1.decrypted
Ananth K. · 评论over 3 years之前
Nurhidayah B. · 评论over 3 years之前
Matheus L. · 评论over 3 years之前
Alex J. · 评论over 3 years之前
Charles E. · 评论over 3 years之前
我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。