You know the way current salting mechanisms work. The server generates a random (e.g., 256 bit) salt for each user during set-up. Hence, the same salt is highly unlikely to be generated for two distinct users. What is stored in the server side are the salt, and Hash(salt \& password). During run-time authentication, the password typed by user and the stored salt for that user are hashed together and compared. You should know this. Now, to keep things simpler, a lazy admin argues that generating and storing salts for so many users is tiresome, and prefers to have ONE long secret at the server side, and for each user, what is stored in the backend is Hash(server secret \& password). Essentially, the salt here is SAME for every user. Identify one problem in this approach from the perspective of security (hint...remember the assignment). Be as descriptive as you can