Encrypting Disks with Customer-Supplied Encryption Keys Reviews

Marek B. · Reviewed almost 7 years ago

Srinath R. · Reviewed almost 7 years ago

Adam A. · Reviewed almost 7 years ago

Patrick B. · Reviewed almost 7 years ago

YASSINE T. · Reviewed almost 7 years ago

Teng Boon L. · Reviewed almost 7 years ago

Nicolas G. · Reviewed about 7 years ago

Vijay M. · Reviewed about 7 years ago

check progress is not working

Subha B. · Reviewed about 7 years ago

Gustavo T. · Reviewed about 7 years ago

Daniel G. · Reviewed about 7 years ago

UI bugs

Paul P. · Reviewed about 7 years ago

Nataraj S. · Reviewed about 7 years ago

good

truong n. · Reviewed about 7 years ago

Eric V. · Reviewed about 7 years ago

Harini S. · Reviewed about 7 years ago

Check my progress buttons are broken

Michael N. · Reviewed about 7 years ago

check progress is not working

Subha B. · Reviewed about 7 years ago

Michael M. · Reviewed about 7 years ago

Lucas M. · Reviewed about 7 years ago

John R. · Reviewed about 7 years ago

Lab: Encrypting Disks with Customer-Supplied Encryption Keys Command: sudo mkfs.ext4 /dev/disk/by-id/google-encrypted-disk-1 Error: google5478494_student@csek-demo:~$ sudo mkfs.ext4 /dev/disk/by-id/google-encrypted-disk-1 mke2fs 1.43.4 (31-Jan-2017) The file /dev/disk/by-id/google-encrypted-disk-1 does not exist and no size was specified. Fixed by specifying the size of the disk: google5478494_student@csek-demo:~$ sudo mkfs.ext4 /dev/disk/by-id/google-encrypted-disk-1 500g mke2fs 1.43.4 (31-Jan-2017) Creating regular file /dev/disk/by-id/google-encrypted-disk-1 Creating filesystem with 131072000 4k blocks and 32768000 inodes Filesystem UUID: 610ca8d7-c52f-41c2-9690-74215139eeb2 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000 Allocating group tables: done Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: done

Ulysses F. · Reviewed about 7 years ago

Nicholas D. · Reviewed about 7 years ago

instructions from step 12 from the mount encrypted disk requires that you input 3 separate steps as opposed to a single command. In addition, the check my status buttons were not appearing so the user had to Run Steps in the upper right summary points section which was not made clear.

Dave R. · Reviewed about 7 years ago

Ashish P. · Reviewed about 7 years ago