Re: [PATCH v11] GSSAPI encryption support

From: Robbie Harwood <rharwood(at)redhat(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH v11] GSSAPI encryption support
Date: 2016-04-01 22:34:56
Message-ID: jlgh9fl3qlr.fsf@thriss.redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello friends,

Song and dance, here's v11 both here and on my github:
https://github.com/frozencemetery/postgres/tree/feature/gssencrypt11

Changes from v10:

- Attempt to address a crash Michael is observing by switching to using
the StringInfo/pqExpBuffer management functions over my own code as
much as possible. Michael, if this doesn't fix it, I'm out of ideas.
Since I still can't reproduce this locally (left a client machine and
a process on the same machine retrying for over an hour on your test
case and didn't see it), could you provide me with some more
information on why repalloc is complaining? Is this a low memory
situation where alloc might have failed? What's your setup look like?
That pointer looks like it's on the heap, is that correct? I really
don't have a handle on what's gone wrong here.

- Switch to using parse_bool for handling gss_encrypt.

- Remove accidental whitespace change.

Thanks!

Attachment Content-Type Size
v11-0001-Move-common-GSSAPI-code-into-its-own-files.patch text/x-diff 15.1 KB
v11-0002-Connection-encryption-support-for-GSSAPI.patch text/x-diff 41.8 KB
v11-0003-GSSAPI-authentication-cleanup.patch text/x-diff 6.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2016-04-01 22:38:38 Re: syntax sugar for conditional check
Previous Message Jim Nasby 2016-04-01 22:22:59 Re: syntax sugar for conditional check