Date: Thu, 17 Feb 2022 11:41:22 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 262011] databases/postgresql14-client: GSSIAPI: remote connection failure Message-ID: <bug-262011-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262011 Bug ID: 262011 Summary: databases/postgresql14-client: GSSIAPI: remote connection failure Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: pgsql@FreeBSD.org Reporter: ohartmann@walstatt.org Flags: maintainer-feedback?(pgsql@FreeBSD.org) Assignee: pgsql@FreeBSD.org When port databases/postgresql1[234]-client is configured with OPTION GSSAPI set to true and compiled, on platforms 13.0-RELENG, 13-STABLE and 14-CURRENT (tested myself, dis not test on any 12), no "remote" connection (via TCP) c= an be made, the psql client just times out. I've tested this misbehaviour so far with bot server and client on the same host and with our department installation which is remote server/client installation with PostgreSQL 12, 13 14 on the above mentioned FreeBSD platforms. When trying to connect to the local db server via "psql -U postgres -d post= gres -h localhost" (alternatively replaced "-h localhost" by "-h 127.0.0.1" or "= -h ::1"), connection is not possible, the client simply times out. The same is from a remote host where I have to provide the target host via -h option ei= ther as its DNS name, its IPv4 or IPv6. Any connection via the local socket (ommiting -h on the local host) works. It took me a time to figure out that enabling GSSAPI on the client and not having any valif GSSAPI configuration provided, results in some mysterious segmentation faults on server side when checking the postgresql logs. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262011-7788>