From: | Russell Foster <russell(dot)foster(dot)coding(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [Patch] Using Windows groups for SSPI authentication |
Date: | 2020-10-13 21:08:55 |
Message-ID: | CA+VXQbJbQyJ6Th-m0ahbxGDiQJ37ucmO7yW=HV285eQAo8sX5g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Right after I sent that I realized that sspi-group was a bad idea, not sure
if that's even a thing. Tried to cancel as it was still in moderation, but
it made it through anyways! You are right, it is very windows specific. I
can make it windows-group as you said, and resubmit.
On Tue, Oct 13, 2020 at 4:32 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Russell Foster <russell(dot)foster(dot)coding(at)gmail(dot)com> writes:
> > I understand your concerns overall, and the solution you propose seems
> > reasonable. But are we just using "windows-group" because the code is not
> > there today to check for a user in another OS group?
>
> It's not clear to me whether Windows groups have exact equivalents in
> other OSes. If we think the concept is generic, I'd be okay with
> spelling the keyword system-group or the like. The patch you
> proposed looked pretty Windows-specific though. Somebody with more
> SSPI knowledge than me would have to opine on whether "sspi-group"
> is a reasonable name.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2020-10-13 21:34:27 | Re: lost replication slots after pg_upgrade |
Previous Message | Tom Lane | 2020-10-13 20:32:21 | Re: [Patch] Using Windows groups for SSPI authentication |