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

From Stephen Frost
Subject Re: [PATCH v20] GSSAPI encryption support
Date
Msg-id 20190404150054.GJ6197@tamriel.snowman.net
Whole thread Raw
In response to Re: [PATCH v20] GSSAPI encryption support  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH v20] GSSAPI encryption support
List pgsql-hackers
Greetings,

* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> 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.

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

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.  I'm testing
with a non-SSL build and will push the fix shortly.

Thanks!

Stephen

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: "WIP: Data at rest encryption" patch and, PostgreSQL 11-beta3
Next
From: Dmitry Dolgov
Date:
Subject: Re: POC: GROUP BY optimization