shishi/doc shishi.texi

[shishi-commit]

CVSROOT:        /cvsroot/shishi
Module name:    shishi
Branch:         
Changes by:     Simon Josefsson <address@hidden>        03/09/29 15:14:22

Modified files:
        doc            : shishi.texi 

Log message:
        Cosmetic fixes.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/shishi/shishi/doc/shishi.texi.diff?tr1=1.92&tr2=1.93&r1=text&r2=text

Patches:
Index: shishi/doc/shishi.texi
diff -u shishi/doc/shishi.texi:1.92 shishi/doc/shishi.texi:1.93
--- shishi/doc/shishi.texi:1.92 Mon Sep 29 05:58:32 2003
+++ shishi/doc/shishi.texi      Mon Sep 29 15:14:22 2003
@@ -6,15 +6,15 @@
 @setfilename shishi.info
 @documentencoding ISO-8859-1
 @include version.texi
address@hidden The Shishi Manual
address@hidden Shishi
 
 @c Unify some of the indices.
 @syncodeindex tp fn
 @syncodeindex pg fn
 
 @copying
-This is @cite{The Shishi Manual}, last updated @value{UPDATED}, for
-Version @value{VERSION} of Shishi.
+This manual is last updated @value{UPDATED} for version
address@hidden of Shishi.
 
 Copyright @copyright{} 2002, 2003 Simon Josefsson.
 
@@ -39,9 +39,10 @@
 @end direntry
 
 @titlepage
address@hidden The Shishi Manual
address@hidden Shishi
address@hidden Kerberos 5 implementation for the GNU system
 @subtitle for version @value{VERSION}, @value{UPDATED}
address@hidden Simon Josefsson (@email{bug-shishi@@josefsson.org})
address@hidden Simon Josefsson
 @page
 @vskip 0pt plus 1filll
 @insertcopying
@@ -2523,7 +2524,7 @@
 reserve two values in this new typed hole, and described how they are
 used to implement STARTTLS.
 
address@hidden Extensible typed hole based on reserved high bit
address@hidden Extensible typed hole based on reserved high bit
 
 When the high bit is set, the remaining 31 bits of the 4 octets are
 treated as an extensible typed hole, and thus form a 31 bit integer
@@ -2547,7 +2548,7 @@
  2147483648      RESERVED.
 @end verbatim
 
address@hidden STARTTLS requested by client (extension mode 1)
address@hidden STARTTLS requested by client (extension mode 1)
 
 When this is sent by the client, the client is requesting the server
 to start TLS negotiation on the TCP stream.  The client MUST NOT start
@@ -2563,14 +2564,14 @@
 case, it should invoke TLS negotiation on the stream.  If any other
 data is received, the client MUST close the TCP stream.
 
address@hidden STARTTLS request accepted by server (extension mode 2)
address@hidden STARTTLS request accepted by server (extension mode 2)
 
 This 4 octet message should be sent by the server when it has received
 the previous 4 octet message.  The message is an acknowledgment of the
 client's request to initiate STARTTLS on the channel.  The server MUST
 then invoke a TLS negotiation.
 
address@hidden Proceeding after successful TLS negotiation
address@hidden Proceeding after successful TLS negotiation
 
 If the TLS negotiation ended successfully, possibly also considering
 client or server policies, the exchange within the TLS protected
@@ -2583,7 +2584,7 @@
 an error to carry out pre-authentication as well.  We are currently
 experimenting with this mode of operation.
 
address@hidden Proceeding after failed TLS negotiation
address@hidden Proceeding after failed TLS negotiation
 
 If the TLS negotiation fails, possibly due to client or server policy
 (e.g., inadequate support of encryption types in TLS, or lack of