Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd
Date
Msg-id 20140328143348.GB18523@momjian.us
Whole thread Raw
In response to Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd  (Bruce Momjian <bruce@momjian.us>)
List pgsql-bugs
On Fri, Mar 28, 2014 at 10:31:06AM -0400, Tom Lane wrote:
> Christoph Berg <cb@df7cb.de> writes:
> > the quoted code bit above in src/backend/libpq/auth.c is utterly
> > broken: for peer authentication, it uses get_user_name(), which yields
> > the *server* user name, not the client's. For that reason, peer
> > authentication in 9.4devel is broken - you can't log in with your user
> > name, but you can just say -U postgres (or what the initdb user was),
> > and it will let you in.
>
> > The attached patch reverts the src/backend/libpq/auth.c portion of
> > 613c6d26bd42dd8c2dd0664315be9551475b8864 and fixes peer auth.
>
> Applied, thanks!

I guess I should have said I was working on an updated patch.  I will
merge my changes in.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd
Next
From: sdl@mnppsaturn.ru
Date:
Subject: BUG #9756: Inconsistent database after OS restart