What happens if an attacker tries to tamper with the Tag (the MAC) and the ciphertext while they are in transit when a message authentication code (MAC) is being used? Give an explanation as to why this attack can never be successful, given that the ability of the target to identify a tampered Tag/ciphertext ensures that it will succeed every time.

Need the below questions answered:  1) Suppose that a merchant’s website stores hashed passwords that have not been salted. Describe an attack to obtain passwords that could be prevented using salted passwords. (Remember, hashes cannot be "decrypted")   2) You know that it is generally not a good practice to create your own authentication systems when standard packages are available to you. But for the purposes of learning, you are doing it anyway. You are trying to decide which hashing algorithm to use when salting and hashing user passwords for the webapp you are building. Of the following hashing algorithms, which is best for hashing passwords? What makes your choice the best option for this scenario? SHA512 MD5 Bcrypt SHA256 3) There are several options for password hashing algorithms other than your choice from above. Do a little Internet investigation and discuss an equivalent or better option than your previous choice. Are there any parameters or settings to that algorithm…

Is it possible to alter the Tag (the MAC) and the ciphertext while they are in transit using a MAC (message authentication code)? The receiver can always identify a changed Tag/ciphertext in this attack, therefore explain why it will not succeed.

The attacker uses the MAC to try to alter the Tag (the encrypted message) (message authentication code). Exactly what are the potential outcomes if I do this? If this attack succeeds, the target will always be able to spot a tampered Tag or ciphertext.