Considering the concept of salted passwords, answer the following questions: a. Bob thinks that generating and storing a random salt value for each user id is a waste. Instead, he is proposing that his system administrators use a cryptographic hash of the user id as its salt. Describe whether this choice impacts the security of salted passwords and include an analysis of the respective search spaces.

Salt helps the attacker to create a separate dictionary for every salt value. Salt is random data that used additional input functions that hash data, such as passwords. Passwords in plain text stored on the system. However, some additional guards developed to protect the user's password against the system.

Explanation:

Salt is randomly generated for each password. The password is processed with the hash function and output that is stored with salt in the database. Hashing is authentication without exposure to plain text passwords.

Salt does not have to be used by humans and defend pre-computed hash attacks. Hash table required to attach. Salt is different who protect the passwords. Users with the same passwords on several websites protect by salt. Salt hashes making hash instances for the same password.

Hashing is a one-way function and used for authentication. Salting is an association with hashed passwords.

Security of salted passwords:

Salt does not protect a lone attacker after one password. An attacker will calculate hash if the password is hash that is maybe a combination of salt + password.

Salt helps if the attacker is attacking a site and wants to break many passwords. Without salt, attackers can quickly attack accounts. With a correctly chosen salt attacker has to start over for each hashed password.

All password attempts are attempting to crack all accounts because hashed can be pre-computed.

i think its d if im not mistaken