cipher, hash, hmac and pkcs configuration to the Irssi SILC's config
file.
- o Add auto-nick support to Irssi, so that the user specified nickname
- would be sent to the server immediately (automatically) after the
- client is connected to the server.
-
o Add PERL scripting support from Irssi CVS.
o Extend the /HELP command to support sub commands or something. So
behaviour and maybe should be removed. The changer should always
get the one it wants and not have the formatted nickname.
+ o Remove the command destructor all together from the client, it is
+ not needed and its usage is buggy when the context is registered
+ to multiple pending commands.
+
o Additions to do after protocol version 1.1:
o Fix the NICK_CHANGE notify handling not to create new entry
TODO/bugs In SILC Server
========================
- o User modes did not show correctly on normal server but looked ok
- on router. Join channel from normal server, join same from router
- and see the user modes. The founder of the channel (on normal server)
- appears correctly on router but incorrectly (no modes) on normal
- server.
-
- o LIST command reply sending is broken. It is possible it does not
- end the list with LIST_END, but sends LIST_ENTRY as last entry.
+ o strerror messages from premature EOF's to signoff messages.
+ (add perhaps a socket error thingy to SilcSockeConnection).
o Backup router related issues
new features without always making the command incompatible to previous
version. To be included in protocol version 1.1.
+ 5. Inviting and banning by public key should be made possible. To be
+ included in protocol version 1.x.
+
+ 6. Add perhaps SILENCE_USERS, SILENCE_OPERS channel user modes which
+ can be used to silence (moderate) normal users and opers (this set
+ only by founder). To be included in protocol version 1.1.
+
+ 7. Channel Message Payload needs slight redesining to include the IV
+ field to the MAC generation of the payload. It is authenticated
+ by the packet's MAC but not by the payload's MAC. Since the IV
+ belongs to the payload, its integrity should be protected by the
+ payload MAC and not alone by packet MAC. To be included in protocol
+ version 1.1.
+
TODO After 1.0
==============