Mohan K wrote:
> Peter,
> It is chicken and egg problem, I still need to enable kerberos in the
> configure script to make sure proper pieces are picked up. But of course
> the configure script fails :).
> If I provide the relevant patches to configure.in script is that acceptable?
> thanks
Probab
Peter,It is chicken and egg problem, I still need to enable kerberos in the configure script to make sure proper pieces are picked up. But of coursethe configure script fails :).If I provide the relevant patches to
configure.in script is that acceptable?thanksOn 2/6/06, Peter Eisentraut <
[EMAIL P
Mohan K wrote:
> Regarding the configure issue:
> The platform is Tru64 Unix 5.1b, the problem I had was we have
> compiled our Kerberos build statically and is installed in a
> directory other than the standard location. The trick adding to LIBS
> did not work as it (krb5support) library needs to
Thanks.As far as using TLS, it is good approach. Although, we don't need complete channel encryption for every transaction or query. I am looking at a more granular approach whereI can decide depending on the security of information exchange whether to encrypt the
channel or not (like using maybe
> Hello Magnus,
>
> Regarding the configure issue:
> The platform is Tru64 Unix 5.1b, the problem I had was we
> have compiled our Kerberos build statically and is installed
> in a directory other than the standard location. The trick
> adding to LIBS did not work as it (krb5support) library n
Hello Magnus,Regarding the configure issue: The platform is Tru64 Unix 5.1b, the problem I had was we havecompiled our Kerberos build statically and is installed in a directory other than the standard location. The trick adding to LIBS
did not work as it (krb5support) library needs to come after th
> > The *REALM* is not checked, however. This can cause problems if you
> > have a multi-realm system (where the realms already trust
> each other,
> > because the KDC has to give out the service ticket) where
> you have the
> > same username existing in multiple realms representing
> differe
* Magnus Hagander ([EMAIL PROTECTED]) wrote:
> The *REALM* is not checked, however. This can cause problems if you have
> a multi-realm system (where the realms already trust each other, because
> the KDC has to give out the service ticket) where you have the same
> username existing in multiple re
> Greetings,
> I was trying to build source build postgres 8.1.x with MIT
> Kerberos 5 1.4.x implementation.
> The whole thing bombs out. After some digging, I had to hack
> the autoconf script (configure.in) to properly account for
> the way the libraries are built for 1.4.x. I don't know
> w
