git.postgresql.org Git - postgresql.git/commitdiff

diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml

index f6b5bfc131ce47322d4eaf9be3018847c5da68cc..b20f1690a7e855cdc16e3b15ab36be20269a32f5 100644 (file)

--- a/doc/src/sgml/protocol.sgml

+++ b/doc/src/sgml/protocol.sgml

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

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml

index e784268512052773718a5ec45446c8207ac1ea4c..e053e2ee34b3923c6551194335707a43efc7e538 100644 (file)

--- a/doc/src/sgml/runtime.sgml

+++ b/doc/src/sgml/runtime.sgml

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>