Tom Lane 7618eaf5f3 Avoid downcasing/truncation of RADIUS authentication parameters.
Commit 6b76f1bb5 changed all the RADIUS auth parameters to be lists
rather than single values.  But its use of SplitIdentifierString
to parse the list format was not very carefully thought through,
because that function thinks it's parsing SQL identifiers, which
means it will (a) downcase the strings and (b) truncate them to
be shorter than NAMEDATALEN.  While downcasing should be harmless
for the server names and ports, it's just wrong for the shared
secrets, and probably for the NAS Identifier strings as well.
The truncation aspect is at least potentially a problem too,
though typical values for these parameters would fit in 63 bytes.

Fortunately, we now have a function SplitGUCList that is exactly
the same except for not doing the two unwanted things, so fixing
this is a trivial matter of calling that function instead.

While here, improve the documentation to show how to double-quote
the parameter values.  I failed to resist the temptation to do
some copy-editing as well.

Report and patch from Marcos David (bug #16106); doc changes by me.
Back-patch to v10 where the aforesaid commit came in, since this is
arguably a regression from our previous behavior with RADIUS auth.

Discussion: https://postgr.es/m/16106-7d319e4295d08e70@postgresql.org
2019-11-13 13:41:04 -05:00
..
2019-10-13 22:10:38 +02:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00
2019-10-25 20:39:41 +02:00
2019-10-25 20:39:41 +02:00
2019-10-25 20:39:41 +02:00
2019-07-05 08:34:54 +02:00
2019-10-25 20:39:41 +02:00
2019-10-25 20:39:41 +02:00
2019-09-08 10:27:29 +02:00
2019-10-25 20:39:41 +02:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00
2019-10-25 20:39:41 +02:00
2019-10-16 13:09:52 +09:00
2019-06-09 11:25:56 +09:00
2019-07-01 12:50:55 -04:00
2019-10-25 20:39:41 +02:00
2019-07-05 08:34:54 +02:00
2019-09-08 10:27:29 +02:00
2019-10-25 20:39:41 +02:00
2019-04-03 17:40:29 -07:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00
2019-10-25 20:39:41 +02:00
2019-09-08 10:27:29 +02:00
2019-10-25 20:39:41 +02:00
2019-10-25 20:39:41 +02:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00
2019-04-08 22:32:46 +02:00
2019-07-14 14:30:27 +02:00
2019-09-08 10:27:29 +02:00
2019-10-25 20:39:41 +02:00
2019-10-25 20:39:41 +02:00
2019-10-25 20:39:41 +02:00
2019-10-25 20:39:41 +02:00
2019-08-13 08:40:17 +02:00
2019-09-08 10:27:29 +02:00
2019-03-29 13:36:24 +01:00
2019-07-01 12:50:55 -04:00
2019-07-01 12:50:55 -04:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00
2019-08-13 08:40:17 +02:00
2019-09-08 10:27:29 +02:00
2019-03-27 23:10:23 +01:00
2019-03-27 23:10:23 +01:00
2019-10-25 20:39:41 +02:00
2019-07-14 14:30:27 +02:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00
2019-09-08 10:27:29 +02:00

<!-- doc/src/sgml/README.links -->

Linking within DocBook documents can be confusing, so here is a summary:


Intra-document Linking
----------------------

<xref>
	use to get chapter/section number from the title of the target
	link, or xreflabel if defined at the target, or refentrytitle if target
        is a refentry;  has no close tag
	http://www.oasis-open.org/docbook/documentation/reference/html/xref.html

<link>
	use to supply text for the link, requires </link>
	http://www.oasis-open.org/docbook/documentation/reference/html/link.html

linkend=
	controls the target of the link/xref, required

endterm=
	for <xref>, allows the text of the link/xref to be taken from a
	different link target title


External Linking
----------------

<ulink>
	like <link>, but uses a URL (not a document target);  requires
	</ulink>; if no text is specified, the URL appears as the link
	text
	http://www.oasis-open.org/docbook/documentation/reference/html/ulink.html

url=
	used by <ulink> to specify the URL, required


Guidelines
----------

- For an internal link, if you want to supply text, use <link>, else
  <xref>.

- Specific nouns like GUC variables, SQL commands, and contrib modules
  usually have xreflabels.

- For an external link, use <ulink>, with or without link text.