From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | josh(at)agliodbs(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Henry B(dot) Hotz" <hotz(at)jpl(dot)nasa(dot)gov>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Fwd: [PATCHES] Preliminary GSSAPI Patches |
Date: | 2007-05-02 07:59:39 |
Message-ID: | 463844EB.8000007@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander wrote:
>>>> Also, last I checked OpenSSL didn't ship with Windows and Kerberos
>>>> encryption did.
>>> How long ago did you check? I've been using OpenSSL on windows for many
>>> years. Actually, it was supported just fine on Windows back when it was
>>> added to PostgreSQL *at least*.
>> I didn't say *available for download*, I said *ship with*. That is, does a
>> Windows Vista Pro box from the factory come with OpenSSL on it? It does
>> come with Microsoft SSPI, although I don't know compatibility issues.
>
> No, of course not. Microsoft OSes don't ship with *any* third party
> software. So yeah, didn't get what you meant, and you do have a point
> there. Provided the SSPI stuff actually does gssapi encryption - but
> I'll trust the people who say it does. I've only ever used the
> authentication parts myself.
I think it's largely irrelevant though - I can't see us shipping a
non-ssl enabled build now (thats not to say we wouldn't add SSPI support
of course).
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2007-05-02 08:13:18 | Re: Getting parse Error at or near character "and" |
Previous Message | friend 4ever | 2007-05-02 07:40:39 | Getting parse Error at or near character "and" |