Re: [HACKERS] SSPI client authentication in non-Windows builds

2011-01-29 Thread Magnus Hagander
On Sat, Jan 29, 2011 at 16:22, Magnus Hagander wrote: > On Sat, Jan 29, 2011 at 16:21, Christian Ullrich wrote: >> * Magnus Hagander wrote: >> >>> However, i think the code path down around the error message is simply >>> incorrect. That #ifdef spaghetti is pretty hard to parse, but it gives >>>

Re: [HACKERS] SSPI client authentication in non-Windows builds

2011-01-29 Thread Stephen Frost
* Magnus Hagander (mag...@hagander.net) wrote: > They were taken out of the main packaging due to them being a PITA to > deal with in general, IIRC. Yes, making it very difficult for those of us who still need them. :( Stephen signature.asc Description: Digital signature

Re: [HACKERS] SSPI client authentication in non-Windows builds

2011-01-29 Thread Magnus Hagander
On Sat, Jan 29, 2011 at 16:21, Christian Ullrich wrote: > * Magnus Hagander wrote: > >> However, i think the code path down around the error message is simply >> incorrect. That #ifdef spaghetti is pretty hard to parse, but it gives >> the wrong error message (we should say it's sspi that's not av

Re: [HACKERS] SSPI client authentication in non-Windows builds

2011-01-29 Thread Christian Ullrich
* Magnus Hagander wrote: However, i think the code path down around the error message is simply incorrect. That #ifdef spaghetti is pretty hard to parse, but it gives the wrong error message (we should say it's sspi that's not available when we have none of the two options) and/or a "duplicate c

Re: [HACKERS] SSPI client authentication in non-Windows builds

2011-01-29 Thread Magnus Hagander
On Sun, Jan 23, 2011 at 16:02, Christian Ullrich wrote: > * Christian Ullrich wrote: > >> Magnus Hagander wrote: > >>> On Mon, Jan 3, 2011 at 14:11, Christian Ullrich >>> wrote: > This change has been tested and works correctly on FreeBSD 8.1, using the Kerberos and GSSAPI libraries from

Re: [HACKERS] SSPI client authentication in non-Windows builds

2011-01-23 Thread Christian Ullrich
* Christian Ullrich wrote: Magnus Hagander wrote: On Mon, Jan 3, 2011 at 14:11, Christian Ullrich wrote: This change has been tested and works correctly on FreeBSD 8.1, using the Kerberos and GSSAPI libraries from Heimdal 1.4. The server is running PostgreSQL 9.0.2 on Windows 2008. Does

Re: [HACKERS] SSPI client authentication in non-Windows builds

2011-01-17 Thread Christian Ullrich
Magnus Hagander wrote: On Mon, Jan 3, 2011 at 14:11, Christian Ullrich wrote: Hello all, this patch adds support for connecting to servers running on Windows and requesting SSPI authentication. It does this by treating AUTH_REQ_SSPI the same as AUTH_REQ_GSS if no native SSPI support is availab

Re: [HACKERS] SSPI client authentication in non-Windows builds

2011-01-17 Thread Magnus Hagander
On Mon, Jan 3, 2011 at 14:11, Christian Ullrich wrote: > Hello all, > > this patch adds support for connecting to servers running on Windows > and requesting SSPI authentication. It does this by treating > AUTH_REQ_SSPI the same as AUTH_REQ_GSS if no native SSPI support is > available. > > In addi

Re: [HACKERS] SSPI client authentication in non-Windows builds

2011-01-04 Thread Christian Ullrich
* Robert Haas wrote: On Mon, Jan 3, 2011 at 8:11 AM, Christian Ullrich wrote: this patch adds support for connecting to servers running on Windows and requesting SSPI authentication. It does this by treating AUTH_REQ_SSPI the same as AUTH_REQ_GSS if no native SSPI support is available. I h

Re: [HACKERS] SSPI client authentication in non-Windows builds

2011-01-03 Thread Robert Haas
On Mon, Jan 3, 2011 at 8:11 AM, Christian Ullrich wrote: > this patch adds support for connecting to servers running on Windows > and requesting SSPI authentication. It does this by treating > AUTH_REQ_SSPI the same as AUTH_REQ_GSS if no native SSPI support is > available. I have to confess that

[HACKERS] SSPI client authentication in non-Windows builds

2011-01-03 Thread Christian Ullrich
Hello all, this patch adds support for connecting to servers running on Windows and requesting SSPI authentication. It does this by treating AUTH_REQ_SSPI the same as AUTH_REQ_GSS if no native SSPI support is available. In addition to being generally useful, this is a workaround to a problem wit