Re: [PATCH v20] GSSAPI encryption support - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH v20] GSSAPI encryption support
Date
Msg-id 7566.1554391003@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH v20] GSSAPI encryption support  (Stephen Frost <sfrost@snowman.net>)
Responses Re: [PATCH v20] GSSAPI encryption support
Re: [PATCH v20] GSSAPI encryption support
Re: [PATCH v20] GSSAPI encryption support
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
>> 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.

> Oh, good point.  Interesting that it still works then.

There must be something about the x86_64 ABI that allows this to
accidentally work -- maybe integers are presumed to be sign-extended
to 64 bits by callee not caller?  I added some logging and verified
that pgstat.c is seeing the correct string value, so it's working
somehow.

> I've got a fix for the missing prototypes, I hadn't noticed the issue
> previously due to always building with SSL enabled as well.

Yeah, I'd just come to the conclusion that it's because I didn't
include --with-openssl, and libpq-be.h's #ifdef nest doesn't expect
that.

BTW, the kerberos test suite takes nearly 4 minutes for me, is
it supposed to be so slow?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: GiST VACUUM
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH v20] GSSAPI encryption support