On Thu, Mar 03, 2005 at 01:20:35PM +0100,
Florian Pflug <[EMAIL PROTECTED]> wrote
a message of 47 lines which said:
> Seems so.. you could try to start the postmaster via strace -f, and
> capture the log
...
> Then try to connect, and see what happens - you should see the
> postmaster open your
Stephane Bortzmeyer <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> wrote
>> so it sure looks like we *are* using getpwuid.
> You're right but I do not understand why it fails only with
> PostgreSQL.
Perhaps one of the pile of random libraries we include is supplying a
broken version
On Thu, Mar 03, 2005 at 12:00:51PM +0100,
Marco Colombo <[EMAIL PROTECTED]> wrote
a message of 39 lines which said:
> Does Debian include and activate SELinux?
Not at all.
---(end of broadcast)---
TIP 2: you can get off all lists at once with th
On Thu, March 3, 2005 12:00, Marco Colombo said:
> On Thu, 3 Mar 2005, Stephane Bortzmeyer wrote:
>> On Thu, Mar 03, 2005 at 10:04:32AM +0100,
>> Florian G. Pflug <[EMAIL PROTECTED]> wrote
>> a message of 114 lines which said:
>>
>>> Might it be that the postgres user is not allowed to read
>>> /et
On Thu, 3 Mar 2005, Stephane Bortzmeyer wrote:
On Thu, Mar 03, 2005 at 10:04:32AM +0100,
Florian G. Pflug <[EMAIL PROTECTED]> wrote
a message of 114 lines which said:
Might it be that the postgres user is not allowed to read
/etc/ldap.conf - or however your nss_ldap config file is called?
myriam:~
On Thu, Mar 03, 2005 at 04:03:25AM -0500,
Tom Lane <[EMAIL PROTECTED]> wrote
a message of 21 lines which said:
> pass = getpwuid(peercred.uid);
>
> so it sure looks like we *are* using getpwuid.
You're right but I do not understand why it fails only with
PostgreSQL.
-
On Thu, Mar 03, 2005 at 10:04:32AM +0100,
Florian G. Pflug <[EMAIL PROTECTED]> wrote
a message of 114 lines which said:
> Might it be that the postgres user is not allowed to read
> /etc/ldap.conf - or however your nss_ldap config file is called?
myriam:~ % ls -ld /etc/*ldap*
drwxr-xr-x 2 ro
Stephane Bortzmeyer wrote:
All the user accounts, including mine, are in a LDAP database. Thanks
to NSS (Name Service Switch) all applications have access to the LDAP
accounts (getpwuid(3) and getpwnam(3) use LDAP). But not PostgreSQL.
I did similar setups and both gentoo and debian/sarge, and this
Stephane Bortzmeyer <[EMAIL PROTECTED]> writes:
> The real issue is "Why PostgreSQL does not use getpwuid when
> getsockopt with SO_PEERCREED returns a numeric UID?"
Oh? I read in hba.c
if (getsockopt(sock, SOL_SOCKET, SO_PEERCRED, &peercred, &so_len) != 0 ||
so_len != sizeof(peercre
On Wed, Mar 02, 2005 at 02:16:29PM -0500,
Tom Lane <[EMAIL PROTECTED]> wrote
a message of 8 lines which said:
> > It is of course very inconvenient to duplicate my LDAP database into
> > pg_ident.conf. Is there a better way?
>
> Perhaps you can find a PAM plugin that talks to LDAP, and configu
Stephane Bortzmeyer <[EMAIL PROTECTED]> writes:
> It is of course very inconvenient to duplicate my LDAP database into
> pg_ident.conf. Is there a better way?
Perhaps you can find a PAM plugin that talks to LDAP, and configure
Postgres to use that.
regards, tom lane
-
I manage a Debian/Linux machine which runs PostgreSQL 7.4.7.
All the user accounts, including mine, are in a LDAP database. Thanks
to NSS (Name Service Switch) all applications have access to the LDAP
accounts (getpwuid(3) and getpwnam(3) use LDAP). But not PostgreSQL.
When I connect locally (Lin
12 matches
Mail list logo
