...............................................................................1988 F.20.2.2. gen_salt() ....................................................................................1989 F.20.3 the server. It first MD5 encrypts it based on the user name, and then encrypts it based on a random salt sent by the server when the database connection was made. It is this double-encrypted value that is different user if you need to do that.) Because MD5-encrypted passwords use the role name as cryptographic salt, renaming a role clears its password if the password is MD5-encrypted. The remaining variants change

...............................................................................1871 F.20.2.2. gen_salt() .............................................................................1872 F.20.3. PGP encryption the server. It first MD5 encrypts it based on the user name, and then encrypts it based on a random salt sent by the server when the database connection was made. It is this double- encrypted value that different user if you need to do that.) Because MD5-encrypted passwords use the role name as cryptographic salt, renaming a role clears its password if the password is MD5- encrypted. The remaining variants change

........................................................................2073 xliv F.23.2.2. gen_salt() .............................................................................2073 F.23.3. PGP encryption the server. It first MD5 encrypts it based on the user name, and then encrypts it based on a random salt sent by the server when the database connection was made. It is this double- encrypted value that must be configured for the server’s user name, not the client’s. Because md5 uses the user name as salt on both the client and server, md5 cannot be used with db_user_namespace. Note: This feature is intended

...............................................................................2209 F.23.2.2. gen_salt() ....................................................................................2209 F.23.3 the server. It first MD5 encrypts it based on the user name, and then encrypts it based on a random salt sent by the server when the database connection was made. It is this double-encrypted value that is must be con- figured for the server’s user name, not the client’s. Because md5 uses the user name as salt on both the client and server, md5 cannot be used with db_user_namespace. Note: This feature is intended

...............................................................................2238 F.25.2.2. gen_salt() .............................................................................2238 F.25.3. PGP encryption the server. It first MD5-encrypts it based on the user name, and then encrypts it based on a random salt sent by the server when the database connection was made. It is this double- encrypted value that must be configured for the server’s user name, not the client’s. Because md5 uses the user name as salt on both the client and server, md5 cannot be used with db_user_namespace. Note: This feature is intended

...............................................................................2947 F.25.2.2. gen_salt() ....................................................................................2947 F.25.3 the server. It first MD5-encrypts it based on the user name, and then encrypts it based on a random salt sent by the server when the database connection was made. It is this double-encrypted value that is must be con- figured for the server’s user name, not the client’s. Because md5 uses the user name as salt on both the client and server, md5 cannot be used with db_user_namespace. Note: This feature is intended

...............................................................................2386 F.25.2.2. gen_salt() ....................................................................................2386 F.25.3 the server. It first MD5-encrypts it based on the user name, and then encrypts it based on a random salt sent by the server when the database connection was made. It is this double-encrypted value that is must be con- figured for the server’s user name, not the client’s. Because md5 uses the user name as salt on both the client and server, md5 cannot be used with db_user_namespace. Note: This feature is intended

...............................................................................2647 F.28.2.2. gen_salt() ....................................................................................2647 F.28.3 the server. It first MD5-encrypts it based on the user name, and then encrypts it based on a random salt sent by the server when the database connection was made. It is this double-encrypted value that is must be con- figured for the server’s user name, not the client’s. Because md5 uses the user name as salt on both the client and server, md5 cannot be used with db_user_namespace. Note: This feature is intended

...............................................................................2777 F.25.2.2. gen_salt() .............................................................................2778 F.25.3. PGP Encryption the server. It first MD5-encrypts it based on the user name, and then encrypts it based on a random salt sent by the server when the database connection was made. It is this double- encrypted value that must be configured for the server’s user name, not the client’s. Because md5 uses the user name as salt on both the client and server, md5 cannot be used with db_user_namespace. Note: This feature is intended

...............................................................................2488 F.28.2.2. gen_salt() .............................................................................2489 F.28.3. PGP Encryption the server. It first MD5-encrypts it based on the user name, and then encrypts it based on a random salt sent by the server when the database connection was made. It is this double- encrypted value that must be configured for the server’s user name, not the client’s. Because md5 uses the user name as salt on both the client and server, md5 cannot be used with db_user_namespace. Note: This feature is intended