From: Pekka Riikonen Date: Mon, 25 Nov 2002 09:26:21 +0000 (+0000) Subject: updates X-Git-Tag: 1.2.beta1~862 X-Git-Url: http://git.silcnet.org/gitweb/?p=crypto.git;a=commitdiff_plain;h=6cb165656920f3a7de6066537df2efb5e7d60653 updates --- diff --git a/doc/draft-riikonen-silc-ke-auth-06.nroff b/doc/draft-riikonen-silc-ke-auth-06.nroff index c54062f4..4424eb48 100644 --- a/doc/draft-riikonen-silc-ke-auth-06.nroff +++ b/doc/draft-riikonen-silc-ke-auth-06.nroff @@ -418,7 +418,7 @@ two SILC clients. In normal case, where client is connecting to a server, or server is connecting to a router the Mutual Authentication flag MAY be omitted. However, if the connection authentication protocol for the connecting entity is not based on digital signatures (it is -on pre-shared key) then the Mutual Authentication flag SHOULD be +based on pre-shared key) then the Mutual Authentication flag SHOULD be enabled. This way the connecting entity has to provide proof of possession of the private key for the public key it will provide in this protocol. diff --git a/doc/draft-riikonen-silc-spec-06.nroff b/doc/draft-riikonen-silc-spec-06.nroff index 81807e13..19cb9365 100644 --- a/doc/draft-riikonen-silc-spec-06.nroff +++ b/doc/draft-riikonen-silc-spec-06.nroff @@ -1263,18 +1263,18 @@ case of CTR mode it refers to the counter block. The format of the Figure 6: Counter Block .in 6 -o Truncated HASH from SKE (4 bytes) - This value is the 32 most - significant bits from the HASH value that was computed as a - result of SKE protocol. This acts as session identifier and - each rekey MUST produce a new HASH value. - -o Sending/Receiving IV from SKE (8 bytes) - This value is the 64 - most significant bits from the Sending IV or Receiving IV - generated in the SKE protocol. When this mode is used to - encrypt sending traffic the Sending IV is used, when used to - decrypt receiving traffic the Receiving IV is used. This - assures that two parties of the protocol use different IV - for sending traffic. Each rekey MUST produce a new value. +o Truncated HASH from SKE (4 bytes) - This value is the first 4 + bytes from the HASH value that was computed as a result of SKE + protocol. This acts as session identifier and each rekey MUST + produce a new HASH value. + +o Sending/Receiving IV from SKE (8 bytes) - This value is the + first 8 bytes from the Sending IV or Receiving IV generated in + the SKE protocol. When this mode is used to encrypt sending + traffic the Sending IV is used, when used to decrypt receiving + traffic the Receiving IV is used. This assures that two parties + of the protocol use different IV for sending traffic. Each rekey + MUST produce a new value. o Block Counter (4 bytes) - This is the counter value for the counter block and is MSB ordered number starting from one (1)