Re: [PoC] Federated Authn/z with OAUTHBEARER
Christoph Berg <myon@debian.org>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
meson: Fix install-quiet after clean
- a9ffb35274fb 18.0 landed
- 4ae03be54734 19 (unreleased) landed
-
oauth: Run Autoconf tests with correct compiler flags
- 3d23f68c5529 18.0 landed
- 990571a08b66 19 (unreleased) landed
-
Link libpq with libdl if the platform needs that.
- 4df477153a6b 19 (unreleased) landed
- 7bd752c1fb8e 18.0 landed
-
Doc: correct spelling of meson switch.
- 3faac9d14063 16.9 landed
- 766d2e673342 17.5 landed
- ac557793d478 18.0 landed
-
oauth: Correct SSL dependency for libpq-oauth.a
- 3db68212a393 18.0 landed
-
oauth: Fix Autoconf build on macOS
- 4ea1254f35b2 18.0 cited
-
oauth: Move the builtin flow into a separate module
- b0635bfda053 18.0 landed
-
Remove a stray "pgrminclude" annotation
- 764d501d24ba 18.0 cited
-
oauth: Simplify copy of PGoauthBearerRequest
- 1cf4c56480f8 18.0 landed
-
oauth: Improve validator docs on interruptibility
- 873c0fd67872 18.0 landed
-
oauth: Disallow synchronous DNS in libcurl
- d7e40845f923 18.0 landed
-
oauth: Fix postcondition for set_timer on macOS
- 434dbf6907ec 18.0 landed
-
oauth: Use IPv4-only issuer in oauth_validator tests
- 8d9d5843b55f 18.0 landed
-
Work around OAuth/EVFILT_TIMER quirk on NetBSD.
- c301a0a74a8a 18.0 landed
-
oauth: Fix incorrect const markers in struct
- 03366b61dfe5 18.0 landed
-
Add missing entry to oauth_validator test .gitignore
- 2c53dec7f440 18.0 landed
-
cirrus: Temporarily fix libcurl link error
- 9d9a71002a1c 18.0 landed
-
Add support for OAUTHBEARER SASL mechanism
- b3f0be788afc 18.0 landed
-
libpq: Handle asynchronous actions during SASL
- a99a32e43ed7 18.0 landed
-
require_auth: prepare for multiple SASL mechanisms
- f8d8581ed882 18.0 landed
-
Move PG_MAX_AUTH_TOKEN_LENGTH to libpq/auth.h
- e21d6f297158 18.0 landed
-
Make SASL max message length configurable
- 6d16f9debae0 18.0 landed
-
jsonapi: fully initialize dummy lexer
- 41b023946dfd 18.0 landed
-
common/jsonapi: support libpq as a client
- 0785d1b8b2fa 18.0 landed
-
Remove fe_memutils from libpgcommon_shlib
- f1976df5eaf2 18.0 landed
-
Revert ECPG's use of pnstrdup()
- f0096ef13be2 13.17 landed
- 3557185538fe 14.14 landed
- 2de129b356bf 15.9 landed
- ee2997c678d8 16.5 landed
- e9e05c655069 17.0 landed
- 5388216f6adc 18.0 landed
-
Explicitly require password for SCRAM exchange
- adcdb2c8dda4 17.0 landed
-
Refactor SASL exchange to return tri-state status
- 24178e235ea5 17.0 landed
Re: Jacob Champion > > > +This module ABI is an internal implementation detail, so it's subject to change > > > +without warning, even during minor releases (however unlikely). The compiled > > > +version of libpq-oauth should always match the compiled version of libpq. > > > > Shouldn't we then include the *minor* version in the soname? > > No objection here. Mmmmh. Since we are currently only talking about 3 symbols, it doesn't sound very likely that we'd have to bump this in a major branch. Putting the minor version into the filename would make looking at package diffs harder when upgrading. Do we really need this as opposed to some hardcoded number like libpq.so.5.18 ? Perhaps reusing the number from libpq.so.5.18 also for this lib would be the way to go? > > Which actually makes me wonder if we ought to instead load the library from a > > specific location... > > We could hardcode the disk location for version 1, I guess. I kind of > liked giving packagers the flexibility they're used to having from the > ld.so architecture, though. See below. pkglibdir or a subdirectory of it might make sense. Though for Debian, I'd actually prefer /usr/lib/$DEB_HOST_MULTIARCH/libpq/libpq-oauth... since the libpq packaging is independent from the major version packaging. > Are there technical downsides of putting it into $libdir? I understand > there are "people" downsides, since we don't really want to signal > that this is a publicly linkable thing... but surely if you go through > the process of linking our library (which has no SONAME, includes the > major/minor version in its -l option, and has no pkgconfig) and > shoving a private pointer to a threadlock into it, you can keep all > the pieces when they break? The Debian Policy expectation is that everything in libdir is a proper library that could be linked to, and that random private stuff should be elsewhere. But if being able to use the default lib search path is an important argument, we could put it there. Christoph