upstream/postgresql
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-04-23 15:19:08 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix typos in documentatoin of GSSAPI encryption

Browse source 
Author: Daniel Gustafsson
Discussion: https://postgr.es/m/5520EDD8-7AC7-4307-8171-400DD1D84FDC@yesql.se
This commit is contained in:
Michael Paquier 2019-05-17 08:22:28 +09:00
parent 75445c1515
commit 41998f90ce
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/src/sgml/protocol.sgml
View file

@ -1502,7 +1502,7 @@ SELECT 1/0;
respectively. The frontend might close the connection at this point
if it is dissatisfied with the response. To continue after
<literal>G</literal>, using the GSSAPI C bindings as discussed in RFC2744
or equivilant, perform a <acronym>GSSAPI</acronym> initialization by
or equivalent, perform a <acronym>GSSAPI</acronym> initialization by
calling <function>gss_init_sec_context()</function> in a loop and sending
the result to the server, starting with an empty input and then with each
result from the server, until it returns no output. When sending the

2
doc/src/sgml/runtime.sgml
View file

@ -2649,7 +2649,7 @@ openssl x509 -req -in server.csr -text -days 365 \
default, this decision is up to the client (which means it can be
downgraded by an attacker); see <xref linkend="auth-pg-hba-conf"/> about
setting up the server to require the use of <acronym>GSSAPI</acronym> for
some or all conections.
some or all connections.
</para>
<para>