Date: Tue, 8 Apr 2025 13:02:11 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Wolfgang Walther <walther@technowledgy.de>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>,
	Daniel Gustafsson <daniel@yesql.se>,
	Christoph Berg <myon@debian.org>,
	Andres Freund <andres@anarazel.de>,
	Peter Eisentraut <peter@eisentraut.org>,
	Tom Lane <tgl@sss.pgh.pa.us>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
	Thomas Munro <thomas.munro@gmail.com>,
	Nazir Bilal Yavuz <byavuz81@gmail.com>,
	Antonin Houska <ah@cybertec.at>
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER
Message-ID: <Z_VWk7Xr-78PV7Cl@momjian.us>
References: 
 <CAOYmi+kt5UvPOXXXT9w_nHBNgcqiTQWS2j=D9qJaewvmO4iaAg@mail.gmail.com>
 <CAOYmi+m2-2TH5AP7-8Knm_gcSiEaZVPGeUkfZeCLmYH395MYgA@mail.gmail.com>
 <B2A4AB83-C99D-4DF7-A310-50BF857739DA@yesql.se>
 <Z_Uzde7a1lCFaqfW@momjian.us>
 <CAOYmi+mrYnuwMEnpYWA4FWFtDCe4rMKavDrKQPpV43u=zmR8Xg@mail.gmail.com>
 <96b5b38b-2fac-409f-b922-f7fd653bf847@technowledgy.de>
 <CAOYmi+m-q8VOPsFxB3D-CWf-T057h4XLqVPvCTudXyAj7-9vpA@mail.gmail.com>
 <bf7c3396-a9a2-4df7-aabd-6fed387e027b@technowledgy.de>
 <CAOYmi+mn_xhkQEyS5KG3zoSOrvskVx8mhD8x_Z+0LL9PaZo1gQ@mail.gmail.com>
 <18f84e6a-41cf-4313-8bea-6007868dd05a@technowledgy.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <18f84e6a-41cf-4313-8bea-6007868dd05a@technowledgy.de>
Archived-At: 
 <https://www.postgresql.org/message-id/Z_VWk7Xr-78PV7Cl%40momjian.us>
Precedence: bulk

On Tue, Apr  8, 2025 at 06:57:18PM +0200, Wolfgang Walther wrote:
> Jacob Champion:
> > On Tue, Apr 8, 2025 at 9:32 AM Wolfgang Walther <walther@technowledgy.de> wrote:
> > > And that should also not be a problem for distributions - they could offer a libpq and a libpq_oauth package, where only one of them can be installed at the same time, I guess? *
> > My outsider understanding is that maintaining this sort of thing
> > becomes a major headache, because of combinatorics. You don't really
> > want to ship a libpq and libpq-with-gss and libpq-with-oauth and
> > libpq-with-oauth-and-gss and ...
> 
> That would only be the case, if you were to consider those other
> dependencies as "dangerous" as cURL. But we already depend on them. So if
> it's really the case that cURL is that much worse, that we consider loading
> it as a module... then the combinatorics should not be a problem either.
> 
> However, if the other deps are considered problematic as well, then the ship
> has already sailed, and there is not point for a special case here anymore.

Yes, I think this is what I am asking too.  For me it was curl's
security reputation and whether that would taint the security reputation
of libpq. For Tom, I think it was the dependency additions.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.