set the key only if application wishes to set (accept the key) it
(Do this to 1.0).
+ o Remove conn->current_channel.
+
o Additions to do after protocol version 1.1:
o Add support for list of errors in command replies. Protocol
payload MAC and not alone by packet MAC. To be included in protocol
version 1.1.
- 11. Change the wording in Private Message Key Payload definition to
- describe the problems of trusting the payload, and to indicate that
- the receiver may not accept the key in the payload, and to describe
- other means of distributing a key.
-
16. Add STATS command after all to the protocol for providing practically
same information client gets when connects to a server. Normal
server would send this to router always when received from client.
+
+ 17. Cell wide channel founder support, and permanent channels when
+ founder mode set.
+
+ 18. Describe the SSH public key, X509, OpenPGP and SPKI certificates
+ encoding format in SKE (from their respective definitions).
+
+ o UTF-8 support/requirement for nicknames & channel names. UTF-8 support
+ in terminals and OS's are so hazy that this matter is left for
+ consideration in next version of the protocol (1.2). For good UTF-8
+ reference and tutorial see: http://www.cl.cam.ac.uk/~mgk25/unicode.html.
+ What should CLI application do if it receives nickname that it cannot
+ display without messing up the terminal? If UTF-8 is mandatory in
+ SILC then SILC clients cannot be allowed to start on terminals that do
+ not support UTF-8 (which renders 98% of users unable to use CLI SILC
+ app without hacking their environment). See also site
+ http://gratrix.net/unicode/
projects / silc.git / blobdiff