Re: Windows: openssl & gssapi dislike each other

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>

To: Andrew Dunstan <andrew@dunslane.net>

Cc: Dave Page <dpage@pgadmin.org>, Imran Zaheer <imran.zhir@gmail.com>, Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2025-01-24T21:45:23Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Move GSSAPI includes into its own header
- e92c0632c147 18.0 landed
Tighten test_predtest's input checks, and improve error messages.
- 00ac25a3c365 17.0 cited
Collation documentation fixes.
- 8ba34c698d19 17.0 cited
contrib/sslinfo needs a fix too to make hamerkop happy.
- 568620dfd691 15.0 cited
Second attempt to silence SSL compile failures on hamerkop.
- 1241fcbd7e64 15.0 cited

> On 24 Jan 2025, at 21:07, Andrew Dunstan <andrew@dunslane.net> wrote:
> On 2025-01-22 We 4:25 AM, Dave Page wrote:

>>  Anyway, no fix was committed as far as I know. I would suggest it should be back-patched as well.
> 
> I'm quite partial to the approach suggested upthread by Andres (a separate pg_gssapi.h file). If there's agreement on that I'm prepared to go and make it happen, unless Daniel beats me to it. Backpatching also seems reasonable.

Thanks for the reminder, I also agree that Andres' suggestion is the best
option.  I hacked up a patch but got distracted by the pgcrypto GUC patch for a
bit.  I'll share what I have once I've done a little testing.

--
Daniel Gustafsson