Repeat the steps from the previous question, but this time use the password: FullSail$1!$

Download the below file: GoodAES$-$GCM$2-$encrypted.txt $($Note the location, you will need it for the decryption$)$

Open Terminal

Use this command to decrypt the data. Add any additional location or directory to the below we need to add the IV and key to properly decrypt the data in a way that also verifies the file was unmodified. To do this we with add the $-$iv and $-$K arguments

openssl enc $-$d $-$aes$-256-$gcm $-$nosalt $-$p $-$in GoodAES$-$GCM$2-$encrypted.txt $-$out GoodAES$-$GCM$2-$decrypted.txt

When prompted for a password enter: FullSail$1!$

The output will still say bad decrypt. The implementation of OpenSSL on Mac ignores the check because the tags are lost in the encryption process. The tags need to be managed and expected which is why they are used for security on data streams that need to protect data and prove the data is unmodified quickly. It$,$ however, makes demonstration in a lab difficult.

Open the GoodAES$2-$decrypted.txt file. What does it say?

Choose one $5$ points

GoodAES$-$GCM$2-$encrypted.txt

$117$ B

This file a good unmodified file that ate every byte of their data just like their parent process told them to$!$

This file a good unmodified file that ate a balanced breakfast of $1$s and $0$s$.$

This file a bad modified file that runs with a bad crowd and got an infection. Now it's malware with nothing to lose!

The file wasn$$t decrypted.