Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL and Kerberos 5 on Solaris

From: "Henry B(dot) Hotz" <hotz(at)jpl(dot)nasa(dot)gov>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: James(dot)Gates(at)Sun(dot)COM, pgsql-ports(at)postgresql(dot)org
Subject: Re: PostgreSQL and Kerberos 5 on Solaris
Date: 2006-09-27 01:04:10
Message-ID: C87E06E7-9B27-4990-B7B3-DB50C246C305@jpl.nasa.gov (view raw or flat)
Thread:
Lists: pgsql-ports
Never saw a followup on this.

I'd suggest krb5_init_context() since it's the first thing any  
Kerberos app needs to do, and the returned context value is used on  
99% of all other calls.  That's assuming that there aren't other  
kerberos checks that make it unnecessary of course.

On Jul 2, 2006, at 8:39 PM, Tom Lane wrote:

> James Gates <James(dot)Gates(at)Sun(dot)COM> writes:
>> Does anyone know why the check for krb5_encrypt() exists in configure
>> when the code doesn't use it?
>
> At the time it was chosen, it was probably a reasonable choice of
> function to probe for to make sure Kerberos libraries are present.
> Do you have a better suggestion?
>
> 			regards, tom lane

------------------------------------------------------------------------ 
----
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry(dot)B(dot)Hotz(at)jpl(dot)nasa(dot)gov, or hbhotz(at)oxy(dot)edu



In response to

Responses

pgsql-ports by date

Next:From: Mike BassettDate: 2006-09-29 16:32:03
Subject: gmake windows
Previous:From: Josh FremerDate: 2006-09-06 00:27:28
Subject: Re: Postgres failed to compile on debian x86

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group