Re: [PATCH v20] GSSAPI encryption support
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
Alvaro Herrera <alvherre@2ndquadrant.com>,
David Steele <david@pgmasters.net>, Joe Conway <mail@joeconway.com>,
Magnus Hagander <magnus@hagander.net>,
Michael Paquier <michael@paquier.xyz>,
Nico Williams <nico@cryptonector.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>,
Robbie Harwood <rharwood@redhat.com>
Date: 2019-04-04T14:52:48Z
Lists: pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes: > * Tom Lane (tgl@sss.pgh.pa.us) wrote: >> I'm not very sure why the integer/pointer confusion in pgstat_bestart >> doesn't cause hard crashes when using gss auth --- or does >> this suite not actually test that? > Isn't it just saying that because of the implicit declaration..? > Once that's fixed, the integer/pointer warning will go away, but > it's actually a pointer in either case, hence why it isn't crashing. Well, if the caller thinks what is being passed back is an int, it will do a 32-to-64-bit widening, which is almost certainly going to result in a corrupted pointer. > The test suite does test GSS authentication and GSS encryption. Hm. I'll poke at this more closely. regards, tom lane
Commits
-
GSSAPI encryption support
- b0b39f72b990 12.0 landed
-
Fix typo
- 57c932475504 9.6.0 cited