Re: Kerberos authentication, Active Directory, and PostgreSQL - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: Kerberos authentication, Active Directory, and PostgreSQL
Date
Msg-id 1255442508.6540.32.camel@fsopti579.F-Secure.com
Whole thread Raw
In response to Kerberos authentication, Active Directory, and PostgreSQL  ("Turner, Ian" <Ian.Turner@deshaw.com>)
Responses Re: Kerberos authentication, Active Directory, and PostgreSQL
Re: Kerberos authentication, Active Directory, and PostgreSQL
Re: Kerberos authentication, Active Directory, and PostgreSQL
List pgsql-bugs
On Mon, 2009-10-12 at 20:42 -0400, Turner, Ian wrote:
> --- postgresql-8.4-8.4.1/src/backend/libpq/auth.c       2009-06-25 12:30:08.000000000 +0100
> +++ postgresql-8.4-8.4.1-fixed/src/backend/libpq/auth.c 2009-09-15 20:27:01.000000000 +0100
> @@ -166,6 +166,8 @@
>  #endif
>
>  static int     pg_GSS_recvauth(Port *port);
> +
> +#define GSS_MAX_TOKEN_LENGTH (32767)
>  #endif   /* ENABLE_GSS */
>
>

A small wish in case we go with this: The constant should be named
something like PG_...; otherwise it looks like we are defining or
overriding an official symbol from the GSS API.

> @@ -937,7 +939,7 @@
>
>                 /* Get the actual GSS token */
>                 initStringInfo(&buf);
> -               if (pq_getmessage(&buf, 2000))
> +               if (pq_getmessage(&buf, GSS_MAX_TOKEN_LENGTH))
>                 {
>                         /* EOF - pq_getmessage already logged error */
>                         pfree(buf.data);

To wit, the above hunk looks quite misleading in isolation.

pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Kerberos authentication, Active Directory, and PostgreSQL
Next
From: Tom Lane
Date:
Subject: Re: Kerberos authentication, Active Directory, and PostgreSQL