Hi On 14-08-16 22:35, Christoph Anton Mitterer wrote: > On Sun, 2016-08-14 at 11:35 +0200, Paul Gevers wrote: > Hmm well I'm still using the dbconfig version from jessie-backports, so > perhaps this is obsolete in later versions?
Nope, that is fully up-to-date. But in your first e-mail you did suggest that you started out with the plain jessie version. Maybe you remember the question from that version. > I find this basically when do the same as where I sent you the debug > log for #830888. > When dbconfig asks me for the auth method for the user and for the > database admin I could choose between ident and something else (forgot > which one, perhaps md5?). ident or password. I guess you are talking about the answers here. The text about the method read (note the quotes): With "ident" authentication on the local machine, the server will check that the owner of the Unix socket is allowed to connect. PostgreSQL itself calls this peer authentication. . With "ident" authentication to remote hosts, RFC-1413-based ident is used (which can be considered a security risk). . With "password" authentication, a password will be passed to the server for use with some authentication backend (such as "MD5" or "PAM"). Note that the password is still passed in the clear across network connections if your connection is not configured to use SSL. . For a standard PostgreSQL installation running on the same host, "ident" is recommended. > I just think using "peer" could cause less (possible) confusion when > the user is asked, as "peer" is rather the "canonical" name for the > "match system-user-name-auth-method", while ident is rather meant for > use ident*d*. When you read the text again, do you think we can clarify more? Internally for dbconfig, peer (localhost) and ident (remote host) are treated identical. For the same reason, also the original name in PostgreSQL was the same. Paul
signature.asc
Description: OpenPGP digital signature
