public inbox for [email protected]help / color / mirror / Atom feed
pgsql: postgres_fdw, dblink: Validate use_scram_passthrough values 2+ messages / 1 participants [nested] [flat]
* pgsql: postgres_fdw, dblink: Validate use_scram_passthrough values @ 2026-05-28 11:59 Fujii Masao <[email protected]> 0 siblings, 0 replies; 2+ messages in thread From: Fujii Masao @ 2026-05-28 11:59 UTC (permalink / raw) To: [email protected] postgres_fdw, dblink: Validate use_scram_passthrough values The use_scram_passthrough option in postgres_fdw and dblink accepts only boolean values. However, unlike other boolean options such as keep_connections, its value was not previously validated. As a result, commands such as "CREATE SERVER ... OPTIONS (use_scram_passthrough 'invalid')" could succeed unexpectedly. This commit updates postgres_fdw and dblink to validate that use_scram_passthrough is assigned a valid boolean value, and throw an error for invalid input. Backpatch to v18, where use_scram_passthrough was introduced. Author: Fujii Masao <[email protected]> Reviewed-by: Ayush Tiwari <[email protected]> Reviewed-by: Matheus Alcantara <[email protected]> Discussion: https://postgr.es/m/CAHGQGwF+-k-Ehsu5W94ZP7GxS3wiBd+mi0PfGTdJ_i2Yr0zR3g@mail.gmail.com Backpatch-through: 18 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/8a86aa313a714adc56c74e4b08793e4e6102b5ca Modified Files -------------- contrib/dblink/dblink.c | 3 +++ contrib/postgres_fdw/option.c | 3 ++- 2 files changed, 5 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: postgres_fdw, dblink: Validate use_scram_passthrough values @ 2026-05-28 11:59 Fujii Masao <[email protected]> 0 siblings, 0 replies; 2+ messages in thread From: Fujii Masao @ 2026-05-28 11:59 UTC (permalink / raw) To: [email protected] postgres_fdw, dblink: Validate use_scram_passthrough values The use_scram_passthrough option in postgres_fdw and dblink accepts only boolean values. However, unlike other boolean options such as keep_connections, its value was not previously validated. As a result, commands such as "CREATE SERVER ... OPTIONS (use_scram_passthrough 'invalid')" could succeed unexpectedly. This commit updates postgres_fdw and dblink to validate that use_scram_passthrough is assigned a valid boolean value, and throw an error for invalid input. Backpatch to v18, where use_scram_passthrough was introduced. Author: Fujii Masao <[email protected]> Reviewed-by: Ayush Tiwari <[email protected]> Reviewed-by: Matheus Alcantara <[email protected]> Discussion: https://postgr.es/m/CAHGQGwF+-k-Ehsu5W94ZP7GxS3wiBd+mi0PfGTdJ_i2Yr0zR3g@mail.gmail.com Backpatch-through: 18 Branch ------ REL_18_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/e5d019fbdc12281f666a94d3d2cf8ad33ae2006a Modified Files -------------- contrib/dblink/dblink.c | 3 +++ contrib/postgres_fdw/option.c | 3 ++- 2 files changed, 5 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2026-05-28 11:59 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-05-28 11:59 pgsql: postgres_fdw, dblink: Validate use_scram_passthrough values Fujii Masao <[email protected]> 2026-05-28 11:59 pgsql: postgres_fdw, dblink: Validate use_scram_passthrough values Fujii Masao <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox