Overview#Salt is a non-secret, random value that's used to ensure that the same message (often a Password) will not consistently hash to the same output value.
Salt is typically used to prevent precomputation attacks such as Rainbow Tables or dictionary attacks.
Salt is generally appended to the clear-text password, which is the encoded using the desired message digest algorithm, and then the clear-text Salt is appended to the message digest and the resulting value is Base64. This makes it possible to determine what the salt was so that it can be used to determine whether a user-supplied password is correct.
The Crypt uses a relatively weak 12-bit Salt, which means that there are only 4096 ways of encoding any value. This is a relatively low number, and therefore it is possible to construct dictionaries of every possible encoding for a wide range of values for use in breaking user passwords. Other Password Storage Scheme in OpenDS use a 64-bit Salt which provide 18446744073709551616 different ways of encoding any one value.
If you Salt#Salted Password Hashing - Doing it Right 
More Information#There might be more information for this subject on one of the following:
- AS Exchange
- Authentication Password Syntax
- Biometric Data Challenges
- Cancelable Biometrics
- Glossary Of LDAP And Directory Terminology
- NT LAN Manager Vulnerabilities
- Nounce or Salt
- Oracle Passwords
- Password Flow From Active Directory to eDirectory
- Password Periodic Changes
- Password Storage Scheme
- Password Validator
- Rich Credential
- [#1] - What is the difference between hash salting and noncing? - based on information obtained 2016-10-28
- [#2] - Salted Password Hashing - Doing it Right - based on information obtained 2016-10-28