From: | Chris Gooch <cgooch(at)bamfunds(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | RE: [EXT] Re: GSS Auth issue when user member of lots of AD groups |
Date: | 2025-05-27 16:13:07 |
Message-ID: | DS0PR22MB597141E2FBF921B3B3480452BE64A@DS0PR22MB5971.namprd22.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-committers |
Thanks again for sharing the patches Tom.
I have just tested the following combinations on v17 and all working as expected, both with tickets less thank 16k and greater than 16k.
1. Patched Client to Unpatched Server
2. Unpatched Client to Patched Server
3. Patched Client to Patched Server
Thanks,
Chris
-----Original Message-----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Sent: Sunday, May 25, 2025 4:51 PM
To: Chris Gooch <cgooch(at)bamfunds(dot)com>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>; pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups
I wrote:
> Chris Gooch <cgooch(at)bamfunds(dot)com> writes:
>> Are there specific test cases you would like me to try?
> Obviously, check if it works for the user with lots of AD groups.
> But beyond that, just check it in everyday use.
Oh --- one specific scenario that would be good to check is to verify that patched libpq can still use GSS with unpatched server and vice versa, so long as the ticket doesn't exceed 16K.
regards, tom lane
This email and any attachments should not be construed as an offer or recommendation to sell or buy or a solicitation of an offer to sell or buy any specific security, fund or instrument or to participate in any particular investment strategy. The information contained herein is given as of a certain date and does not purport to give information as of any other date. Although the information presented herein has been obtained from sources we believe to be reliable, no representation or warranty, expressed or implied, is made as to the accuracy or completeness of that information. Past performance is not indicative of future results.
CONFIDENTIALITY NOTICE: This message and any attachment are confidential. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other persons.
Balyasny Asset Management (UK) LLP is authorised and regulated by the Financial Conduct Authority in the UK. Balyasny Asset Management LP is registered as an Investment Advisor with the Securities and Exchange Commission in the USA.
BAM prohibits all personnel from having any business related communications over text message or other unapproved communication applications. Unless pre-approved, BAM employees are only permitted to communicate over email, Bloomberg and BAM telephone lines.
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2025-05-27 21:05:17 | Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 |
Previous Message | Tom Lane | 2025-05-27 14:54:12 | Re: SIMILAR TO expressions translate wildcards where they shouldn't |
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2025-05-27 18:44:49 | pgsql: Fix assertion when decrementing eager scanning success and failu |
Previous Message | Peter Eisentraut | 2025-05-26 13:20:33 | pgsql: Improve file_copy_method entry in postgresql.conf.sample |