pgsql: Introduce safer encoding and decoding routines for base64.c

Introduce safer encoding and decoding routines for base64.c

This is a follow-up refactoring after 09ec55b and b674211, which has
proved that the encoding and decoding routines used by SCRAM have a
poor interface when it comes to check after buffer overflows. This adds
an extra argument in the shape of the length of the result buffer for
each routine, which is used for overflow checks when encoding or
decoding an input string. The original idea comes from Tom Lane.

As a result of that, the encoding routine can now fail, so all its
callers are adjusted to generate proper error messages in case of
problems.

On failure, the result buffer gets zeroed.

Author: Michael Paquier
Reviewed-by: Daniel Gustafsson
Discussion: https://postgr.es/m/20190623132535.GB1628@paquier.xyz

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/cfc40d384ae51ea2886d599d2008ae57b529e6ea

Modified Files
--------------
src/backend/libpq/auth-scram.c | 74 +++++++++++++++++++++++++++---------
src/common/base64.c | 59 ++++++++++++++++++++++++----
src/common/scram-common.c | 59 +++++++++++++++++++++++++---
src/include/common/base64.h | 4 +-
src/interfaces/libpq/fe-auth-scram.c | 60 +++++++++++++++++++++++------
5 files changed, 210 insertions(+), 46 deletions(-)