| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: rolcanlogin vs. the flat password file |
| Date: | 2007-10-14 20:56:25 |
| Message-ID: | 12456.1192395385@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Glaesemann <grzm(at)seespotcode(dot)net> writes:
> Would there be a difference in how this is logged and how it's
> reported to the user?
Not without making all the same infrastructure changes that would be
needed to tell the user something different than now. As things stand,
the password auth code can't tell the difference between a nonexistent
role and a nologin role; neither one has an entry in the flat file.
If we dropped the filtering in flatfiles.c, then a nologin role would
have an entry, but most likely without a password, so you'd still just
see "password auth failed".
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-14 21:02:43 | Re: rolcanlogin vs. the flat password file |
| Previous Message | Stephen Frost | 2007-10-14 20:51:12 | Re: rolcanlogin vs. the flat password file |