From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
---|---|
To: | mahendrakar s <mahendrakarforpg(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Subject: | Re: Increase limit on max length of the password( pg versions < 14) |
Date: | 2023-07-18 12:12:45 |
Message-ID: | 50872cc9-5461-7973-058b-20ae338cf969@postgresfriends.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7/18/23 11:30, mahendrakar s wrote:
> Hi hackers,
>
> We have encountered an issue (invalid message length) when the
> password length is > 1000 in pg 11,12,13 versions. This is due to the
> limit(1000) on the max length of the password. In this case the
> password is an access token(JWT) which can have varied lengths >
> 1000. I see that this is already handled for GSS and SSPI
> authentication tokens where the maximum accepted size is 65535.
>
> This is not the case with pg versions >=14 as the limit on max length
> is 65535(this change was added as part of sanity checks[1]).
>
> So we have two options:
> 1. Backport patch[1] to 11,12,13
> 2. Change ONLY the limit on the max length of the password(my patch attached).
>
> Please let me know your thoughts.
The third option is to upgrade.
--
Vik Fearing
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2023-07-18 12:47:19 | Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication |
Previous Message | mahendrakar s | 2023-07-18 11:23:00 | Re: Increase limit on max length of the password( pg versions < 14) |