From: Pekka Riikonen Date: Tue, 27 Mar 2001 11:08:03 +0000 (+0000) Subject: updates. X-Git-Tag: 1.2.beta1~2411 X-Git-Url: http://git.silcnet.org/gitweb/?p=runtime.git;a=commitdiff_plain;h=e0259897e2341f382fc152b022afaee90fd52f7c updates. --- diff --git a/CHANGES b/CHANGES index bb857d32..6709e2d6 100644 --- a/CHANGES +++ b/CHANGES @@ -1,3 +1,26 @@ +Tue Mar 27 12:49:56 EEST 2001 Pekka Riikonen + + * Cleaned up the CMODE command in the server. It now works + correctly and supports all the modes defined in the protocol. + Affected file is silcd/command.c. + + * Added `hmac_name' field to the SilcChannelEntry in the server + to hold the default HMAC of the channel. It can be set when + creating the channel (with JOIN command). Affected files + silcd/idlist.[ch]. + + * Added and argument to the CMODE_CHANGE notify + type to indicate the change of the current cipher and hmac + on the channel. Client can safely ignore the argument + (if it chooses to do so) since the CHANNEL_KEY packet will + force the channel key change anyway. The argument is + important since the client is responsible of setting the new + HMAC and the hmac key into use. + + * Fixed the CMODE command in the client library as well. + + * Tested CMODE command in router environment successfully. + Mon Mar 26 14:39:48 EEST 2001 Pekka Riikonen * Show the version of the remote client (or server) when connecting diff --git a/README b/README index dfff7705..3a339ef3 100644 --- a/README +++ b/README @@ -87,6 +87,7 @@ SILC Commands a Set/unset passphrase for channel that must be provided when joining to the channel. c Set/unset channel's cipher + h Set/unset channel's hmac Multiple modes can be set/unset at once if the modes does not require any arguments. If mode requires an argument then only diff --git a/TODO b/TODO index b8b30a67..95632115 100644 --- a/TODO +++ b/TODO @@ -196,6 +196,10 @@ TODO in the protocol before SILC 0.x flags and define the flags. The flags could indicate whether the message is, for example autoreply or the receiver should not reply to the private messages. What other flags? + o Define the Channel Message packet to include channel message + flags and define the flags. Actually the flags should be same + as for the private message flags. This way we can implement + for example the CTCP style ACTION (/ME command) messages. o New feature in the KE/auth protocol (draft-riikonen-silc-ke-auth-xx.txt):