From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chris Gooch <cgooch(at)bamfunds(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: GSS Auth issue when user member of lots of AD groups |
Date: | 2025-05-22 17:11:53 |
Message-ID: | CAOYmi+mPdZwNe16yozk40G8hW3d1Rxnoipu0dw52AiuZRoabaA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-committers |
On Thu, May 22, 2025 at 9:57 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'm wondering though if this isn't just pushing the problem out a
> little further. Is there a good reason to think 64K is enough?
Microsoft docs [1] seem to imply that there are still a bunch of
existing problems if you try to go much higher, though it is possible
to do so with registry tweaks. Looks like they default to 48k.
Maybe we should consider making the max incoming ticket size
configurable, so users that really need a bigger one can deal with the
DoS risk without it affecting everyone else. (A limit on outgoing
tickets probably doesn't make too much sense; I imagine you're going
to use the ticket that GSSAPI hands you, no matter how big it is,
because it's not as if you have a choice.)
--Jacob
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-05-22 17:58:33 | Re: GSS Auth issue when user member of lots of AD groups |
Previous Message | Chris Gooch | 2025-05-22 17:04:32 | Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-05-22 17:52:54 | pgsql: Fix memory leak in XMLSERIALIZE(... INDENT). |
Previous Message | Chris Gooch | 2025-05-22 17:04:32 | Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups |