Re: BUG #13854: SSPI authentication failure: wrong realm name used

From: Christian Ullrich <chris(at)chrullrich(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: BUG #13854: SSPI authentication failure: wrong realm name used
Date: 2016-01-10 18:08:37
Message-ID: n6u6n5$6fh$1@ger.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

* Christian Ullrich wrote:

> * Christian Ullrich wrote:
>
> > According to the release notes, the default for the "include_realm"
> > option in SSPI authentication was changed from off to on in 9.5 for
> > improved security. However, the authenticated user name, with the
> > option enabled, includes the NetBIOS domain name, *not* the Kerberos
> > realm name:

> Below is a patch to correct this behavior. I suspect it has some
> serious compatibility issues, so I would appreciate feedback.

Updated patch, sorry. The first one worked by accident only.

--
Christian

Attachment Content-Type Size
sspirealm.patch text/plain 7.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-01-10 18:25:40 Why doesn't src/backend/port/win32/socket.c implement bind()?
Previous Message Christian Ullrich 2016-01-10 17:30:43 Re: BUG #13854: SSPI authentication failure: wrong realm name used

Browse pgsql-bugs by date

  From Date Subject
Next Message igal 2016-01-10 18:23:01 BUG #13859: pg_upgrade permissions on Windows
Previous Message Christian Ullrich 2016-01-10 17:30:43 Re: BUG #13854: SSPI authentication failure: wrong realm name used