postgresql/contrib
Tom Lane 67a472d71c Remove arbitrary restrictions on password length.
This patch started out with the goal of harmonizing various arbitrary
limits on password length, but after awhile a better idea emerged:
let's just get rid of those fixed limits.

recv_password_packet() has an arbitrary limit on the packet size,
which we don't really need, so just drop it.  (Note that this doesn't
really affect anything for MD5 or SCRAM password verification, since
those will hash the user's password to something shorter anyway.
It does matter for auth methods that require a cleartext password.)

Likewise remove the arbitrary error condition in pg_saslprep().

The remaining limits are mostly in client-side code that prompts
for passwords.  To improve those, refactor simple_prompt() so that
it allocates its own result buffer that can be made as big as
necessary.  Actually, it proves best to make a separate routine
pg_get_line() that has essentially the semantics of fgets(), except
that it allocates a suitable result buffer and hence will never
return a truncated line.  (pg_get_line has a lot of potential
applications to replace randomly-sized fgets buffers elsewhere,
but I'll leave that for another patch.)

I built pg_get_line() atop stringinfo.c, which requires moving
that code to src/common/; but that seems fine since it was a poor
fit for src/port/ anyway.

This patch is mostly mine, but it owes a good deal to Nathan Bossart
who pressed for a solution to the password length problem and
created a predecessor patch.  Also thanks to Peter Eisentraut and
Stephen Frost for ideas and discussion.

Discussion: https://postgr.es/m/09512C4F-8CB9-4021-B455-EF4C4F0D55A0@amazon.com
2020-09-03 20:09:18 -04:00
..
adminpack Read until EOF vice stat-reported size in read_binary_file 2020-07-04 06:26:53 -04:00
amcheck snapshot scalability: Don't compute global horizons while building snapshots. 2020-08-12 16:03:49 -07:00
auth_delay
auto_explain Add the option to report WAL usage in EXPLAIN and auto_explain. 2020-04-06 08:02:15 +05:30
bloom Invent "amadjustmembers" AM method for validating opclass members. 2020-08-01 17:12:47 -04:00
bool_plperl
btree_gin
btree_gist Make contrib modules' installation scripts more secure. 2020-08-10 10:44:42 -04:00
citext Make contrib modules' installation scripts more secure. 2020-08-10 10:44:42 -04:00
cube Make contrib modules' installation scripts more secure. 2020-08-10 10:44:42 -04:00
dblink Initialize dblink remoteConn struct in all cases 2020-05-28 13:44:54 -04:00
dict_int
dict_xsyn
earthdistance Make contrib modules' installation scripts more secure. 2020-08-10 10:44:42 -04:00
file_fdw Redefine pg_class.reltuples to be -1 before the first VACUUM or ANALYZE. 2020-08-30 12:21:51 -04:00
fuzzystrmatch
hstore Remove no-longer-usable hstore--1.0--1.1.sql update script. 2020-08-15 12:04:19 -04:00
hstore_plperl Make contrib modules' installation scripts more secure. 2020-08-10 10:44:42 -04:00
hstore_plpython
intagg Make contrib modules' installation scripts more secure. 2020-08-10 10:44:42 -04:00
intarray Make contrib modules' installation scripts more secure. 2020-08-10 10:44:42 -04:00
isn
jsonb_plperl Support infinity and -infinity in the numeric data type. 2020-07-22 19:19:44 -04:00
jsonb_plpython Support infinity and -infinity in the numeric data type. 2020-07-22 19:19:44 -04:00
lo
ltree Make contrib modules' installation scripts more secure. 2020-08-10 10:44:42 -04:00
ltree_plpython
oid2name Remove arbitrary restrictions on password length. 2020-09-03 20:09:18 -04:00
pageinspect Avoid using %c printf format for potentially non-ASCII characters. 2020-06-29 11:41:19 -04:00
passwordcheck passwordcheck: Log cracklib diagnostics 2020-08-28 08:18:24 +02:00
pg_buffercache
pg_freespacemap
pg_prewarm Make xact.h usable in frontend. 2020-08-17 10:50:13 +03:00
pg_standby
pg_stat_statements pg_stat_statements: track number of rows processed by some utility commands. 2020-07-29 23:21:55 +09:00
pg_trgm Make contrib modules' installation scripts more secure. 2020-08-10 10:44:42 -04:00
pg_visibility snapshot scalability: Don't compute global horizons while building snapshots. 2020-08-12 16:03:49 -07:00
pgcrypto Replace remaining StrNCpy() by strlcpy() 2020-08-10 23:20:37 +02:00
pgrowlocks
pgstattuple Redefine pg_class.reltuples to be -1 before the first VACUUM or ANALYZE. 2020-08-30 12:21:51 -04:00
postgres_fdw Redefine pg_class.reltuples to be -1 before the first VACUUM or ANALYZE. 2020-08-30 12:21:51 -04:00
seg Make contrib modules' installation scripts more secure. 2020-08-10 10:44:42 -04:00
sepgsql Fix compilation warnings with libselinux 3.1 in contrib/sepgsql/ 2020-08-14 09:30:34 +09:00
spi
sslinfo
start-scripts
tablefunc
tcn
test_decoding Add regression tests for REPLICA IDENTITY with dropped indexes 2020-08-26 20:42:27 +09:00
tsm_system_rows
tsm_system_time
unaccent Update Unicode data to Unicode 13.0.0 and CLDR 37 2020-04-24 09:52:59 +02:00
uuid-ossp
vacuumlo Remove arbitrary restrictions on password length. 2020-09-03 20:09:18 -04:00
xml2
contrib-global.mk
Makefile
README

The PostgreSQL contrib tree
---------------------------

This subtree contains porting tools, analysis utilities, and plug-in
features that are not part of the core PostgreSQL system, mainly
because they address a limited audience or are too experimental to be
part of the main source tree.  This does not preclude their
usefulness.

User documentation for each module appears in the main SGML
documentation.

When building from the source distribution, these modules are not
built automatically, unless you build the "world" target.  You can
also build and install them all by running "make all" and "make
install" in this directory; or to build and install just one selected
module, do the same in that module's subdirectory.

Some directories supply new user-defined functions, operators, or
types.  To make use of one of these modules, after you have installed
the code you need to register the new SQL objects in the database
system by executing a CREATE EXTENSION command.  In a fresh database,
you can simply do

    CREATE EXTENSION module_name;

See the PostgreSQL documentation for more information about this
procedure.