A checksum, also called a message digest, is a small block of data, usually derived from a much larger file, for the purpose of detecting errors that may have been introduced $($either naturally or intentionally$)$ during the transmission of the file. So$,$ the checksum can be used to verify the integrity of the received or downloaded file. The procedure which generates this checksum is called a checksum function or checksum algorithm. Depending on its design goals, a good checksum algorithm usually generates a significantly different value, even for tiny changes made to the input. This is especially true of cryptographic hash functions $($e$.$g$.$ SHA$256$ and MD$5),$ which may be used to detect many data corruption errors and verify overall data integrity. If the computed checksum for the received$/$downloaded data matches the value of a previously computed checksum of the original data, there is a very high probability that the data has not been altered or corrupted during transmission.

Depending on the operating system we use, there are different tools for the checksum, but the process is the same. Here is a list of options for the SHA$256$ and the MD$5$ checksums:

Linux

sha$256$sum $/$path$/$to$/$file

md$5$sum $/$path$/$to$/$file

Mac

shasum $-$a $256/$path$/$to$/$file

md$5/$path$/$to$/$file

Windows

CertUtil $-$hashfile C:$\backslash$path$\backslash$to$\backslash$file SHA$256$

CertUtil $-$hashfile C:$\backslash$path$\backslash$to$\backslash$file MD$5$

When we run the checksum tool, the output of the cryptographic hash algorithm will be just a string of characters. For example, the following is the SHA$256$ checksum of the Tor Browser $($version $13\mathrm{.}0\mathrm{.}14$ for Windows$)$ official installation file:

$8738$a$94$ae$5290$d$577$f$3$aa$700$e$918239$a$4$bcdbe$91$d$41$d$201434$dc$93620617997$b

Your task for this assignment is to verify the balance of your bank account. Simply checking your ebanking account is not good enough because you don$$t trust that your bank$$s systems are free of bugs and malware. That$$s why you always keep a checksum of your most$-$recently verified bank statement. Although you don't remember what the exact balance was the last time you calculated the checksum, you do know that the balance was a whole number, it was a power of $2,$ and you're pretty sure that the amount was less than $$100$K$.$ Moreover, you remember that the last bank statement you calculated the checksum on$,$ was issued on March $31,$ and you know for sure that there haven't been any changes in the balance since then.

After downloading today$$s $($April $24)$ bank statement, you realize that the balance cannot be correct.

Multiple Attempts Not allowed. This test can only be taken once.

Force Completion This test can be saved and resumed later.

Your answers are saved automatically.

Expand Question Completion Status:

QUESTION $1$

What is the SHA $256$ checksum of today's $($April $24)$ bank statement that you just downloaded?

$9$b$378$fcabe$765448$ae$51$ce$07847944$fcd$361$da$0$ad$003$cd$8$be$994$e$11$dcbb$4$e$160$

$1$ points

QUESTION $2$

If the stored SHA$256$ checksum of your last bank statement is the following, what is the correct balance in your account?

$6175$dd$796$cc$1101$c$671$a$6$a$4$da$8$c$61$c$21$de$22$e$2$fcd$65$ac$1$a$611$e$0$c$7$af$8$c$1873$f$9$