mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-10-02 07:11:16 +02:00
9fd85570d1
The code of SCRAM and SASL have been tightly linked together since SCRAM exists in the core code, making hard to apprehend the addition of new SASL mechanisms, but these are by design different facilities, with SCRAM being an option for SASL. This refactors the code related to both so as the backend and the frontend use a set of callbacks for SASL mechanisms, documenting while on it what is expected by anybody adding a new SASL mechanism. The separation between both layers is neat, using two sets of callbacks for the frontend and the backend to mark the frontier between both facilities. The shape of the callbacks is now directly inspired from the routines used by SCRAM, so the code change is straight-forward, and the SASL code is moved into its own set of files. These will likely change depending on how and if new SASL mechanisms get added in the future. Author: Jacob Champion Reviewed-by: Michael Paquier Discussion: https://postgr.es/m/3d2a6f5d50e741117d6baf83eb67ebf1a8a35a11.camel@vmware.com |
||
|---|---|---|
| .. | ||
| auth.h | ||
| be-fsstubs.h | ||
| be-gssapi-common.h | ||
| crypt.h | ||
| hba.h | ||
| ifaddr.h | ||
| libpq-be.h | ||
| libpq-fs.h | ||
| libpq.h | ||
| pqcomm.h | ||
| pqformat.h | ||
| pqmq.h | ||
| pqsignal.h | ||
| sasl.h | ||
| scram.h | ||