Robbie,
* Robbie Harwood (rharw...@redhat.com) wrote:
> I've coded up the GSSAPI encryption and is on my github[0]. It's
> missing a number of things before merge, including proper error
> handling, correct ACL behavior (by and large, it currently doesn't
> respect hba.conf), and exposing configu
Robbie Harwood writes:
> Stephen Frost writes:
>
>> Robbie,
>>
>> * Robbie Harwood (rharw...@redhat.com) wrote:
>>
>>> We'd I think also want a new kind of HBA entry (probably something along
>>> the lines of `hostgss` to contrast with `hostssl`), but I'm not sure
>>> what we'd want to do for th
Stephen Frost writes:
> Robbie,
>
> * Robbie Harwood (rharw...@redhat.com) wrote:
>
>> We'd I think also want a new kind of HBA entry (probably something along
>> the lines of `hostgss` to contrast with `hostssl`), but I'm not sure
>> what we'd want to do for the counterpart of `hostnossl` (`host
Robbie,
* Robbie Harwood (rharw...@redhat.com) wrote:
> Today, there exists GSSAPI authentication support in Postgres. I plan
> to extend this work to include encryption as well, but wanted to get
> your input on that first since you've probably thought about this
> already.
Great!
> From what
Hello!
Today, there exists GSSAPI authentication support in Postgres. I plan
to extend this work to include encryption as well, but wanted to get
your input on that first since you've probably thought about this
already.
From what I can tell, the auth/encryption layer is very nicely designed
for
