Thread: BUG #8365: Two documentation suggestions
The following bug has been logged on the website: Bug reference: 8365 Logged by: David Tonhofer Email address: bughunt@gluino.name PostgreSQL version: 9.2.4 Operating system: Linux Description: Suggestions for documentation: "http://www.postgresql.org/docs/9.2/static/auth-pg-hba-conf.html" ----- "Quoting one of the keywords in a database, user, or address field (e.g., all or replication) makes the word lose its special character," -> Replace "character" by "meaning" for clarity. ----- "Require the client to supply an MD5-encrypted password for authentication." -> Replace "encrypted" by "hashed" (as done in http://www.postgresql.org/docs/9.2/static/auth-methods.html#AUTH-PASSWORD ). -> Actually this should be "Require the client to supply an MD5 hash based on a password for authentication." ...as the exchange is more complex than just supplying a hash.
On Tue, Aug 6, 2013 at 08:31:40AM +0000, bughunt@gluino.name wrote: > "http://www.postgresql.org/docs/9.2/static/auth-pg-hba-conf.html" > > > ----- > > > "Quoting one of the keywords in a database, user, or address field (e.g., > all or replication) makes the word lose its special character," > > > -> Replace "character" by "meaning" for clarity. > > > ----- > > > "Require the client to supply an MD5-encrypted password for > authentication." > > > -> Replace "encrypted" by "hashed" (as done in > http://www.postgresql.org/docs/9.2/static/auth-methods.html#AUTH-PASSWORD ). > > > > > -> Actually this should be > > > "Require the client to supply an MD5 hash based on a password for > authentication." > > > ...as the exchange is more complex than just supplying a hash. I ended up modifying the lines you suggested; applied patch attached. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. +