pgsql: Properly close token in sspi authentication

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Properly close token in sspi authentication
Date: 2016-01-14 12:09:39
Message-ID: E1aJgih-0002zF-4y@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Properly close token in sspi authentication

We can never leak more than one token, but we shouldn't do that. We
don't bother closing it in the error paths since the process will
exit shortly anyway.

Christian Ullrich

Branch
------
REL9_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/ab49f87d5cd4f70fdfe606449ebe1369aa6cbb61

Modified Files
--------------
src/backend/libpq/auth.c | 2 ++
1 file changed, 2 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-01-14 16:52:02 pgsql: Fix build_grouping_chain() to not clobber its input lists.
Previous Message Tom Lane 2016-01-13 23:55:53 pgsql: Handle extension members when first setting object dump flags in