From 41998f90ce66425ca6071ac5e170a19bb1498414 Mon Sep 17 00:00:00 2001 From: Michael Paquier Date: Fri, 17 May 2019 08:22:28 +0900 Subject: [PATCH] Fix typos in documentatoin of GSSAPI encryption Author: Daniel Gustafsson Discussion: https://postgr.es/m/5520EDD8-7AC7-4307-8171-400DD1D84FDC@yesql.se --- doc/src/sgml/protocol.sgml | 2 +- doc/src/sgml/runtime.sgml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index f6b5bfc131..b20f1690a7 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -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 G, using the GSSAPI C bindings as discussed in RFC2744 - or equivilant, perform a GSSAPI initialization by + or equivalent, perform a GSSAPI initialization by calling gss_init_sec_context() 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 e784268512..e053e2ee34 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -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 about setting up the server to require the use of GSSAPI for - some or all conections. + some or all connections. -- 2.40.0