1 TODO/bugs in Irssi SILC client
2 ==============================
4 o Add local command to switch the channel's private key when channel has
5 several private keys. Currently sending channel messages with many
6 keys is not possible because changing the key is not possible by the
9 o JOINing to +a (requires passphrase to JOIN) does not work on autojoin.
10 Seems the passwords in the .silc/config has no effect.
12 o Add local commands to list the current server and client public keys
13 that the user has. And a local command to dump the contents of the
14 public key to the screen. Something like LISTKEYS, SHOWKEY...
16 o The JOIN command's HELP is generated from Irssi IRCs JOIN help and
17 the syntax is not same in SILC. This must be fixed. Most likely
18 we must forget the Irssi's JOIN command and mimic it to get our
19 required syntax for it too.
21 o We should get rid of the clientconfig.[ch] in Irssi SILC and move the
22 cipher, hash, hmac and pkcs configuration to the Irssi SILC's config
25 o Add PERL scripting support from Irssi CVS.
27 o Extend the /HELP command to support sub commands or something. So
28 that user can say /help set mutual_authentication they would get
29 help of the mutual_authentication setting.
31 o Set different kind of settings, like, /set mutual_authentication,
32 /set key_exchange_timeout, /set conn_auth_timeout etc etc.
35 TODO/bugs In SILC Client Library
36 ================================
38 o JOIN command's argument handling is buggy. See the XXX in the code.
41 TODO/bugs In SILC Server
42 ========================
44 o Implement the <founder auth> and founder privileges gaining to
45 the JOIN command. This will bypass invite-only mode as well for
46 the client who got the founder mode during JOIN.
48 o After backup resume protocol the TOPIC_SET was not handled correctly
49 by all (unknown Channel ID).
51 o Channel user mode changes are notified unnecessarely when switching
52 to backup router on router crash.
54 o Change the server to connect to another server from low ports (706)
55 and not from high ports. Currently we cannot do incoming connection
56 checking by remote port because the port is not fixed.
58 o Announcements are incomplete: channel topics are not announced,
59 user modes (UMODE) are not announced.
61 o If client's public key is saved in the server (and doing public key
62 authentication) then the hostname and the username information could
63 be taken from the public key. Should be a configuration option!
65 o Add a timeout to handling incoming JOIN commands. It should be
66 enforced that JOIN command is executed only once in a second or two
67 seconds. Now it is possible to accept n incoming JOIN commands
68 and process them without any timeouts. THis must be employed because
69 each JOIN command will create and distribute the new channel key
70 to everybody on the channel.
72 o Optimize the WHOIS and IDENTIFY commands to somehow check whether the
73 requested clients are on some channel that the server knows about. If
74 this is the case then the request is not needed to be forwarded to the
75 router. One specific optimization could be done with JOIN command.
76 If the previous command to the WHOIS and IDENTIFY commands are JOIN
77 command (from the client) it can be expected (though it must be
78 verified) that the client is resolving the users on the channel it just
79 joined. If server has done this once there is really no reason to
80 resolve it twice (from the router), it can reply directly back with
81 the information it knows. This is because the server would (will)
82 receive notifications from the router for users that are on a local
85 The same is with whowas command. Actually with all these commands
86 it should be checked also whether the requested information is local.
87 If it is, there is no reason to send it to the router, since the server
90 o New configuration file format must be added. The new one will be
91 done using the dotconf config library (lib/dotconf). The following
92 tasks relates closely to this as well and must be done at the same time
93 when adding the new config file format:
95 o Server says that it is able to listen on multiple ports but
96 currently that is bogus. It can, but internals are for single
99 o Protocol execution timeouts are hard coded, should be
102 o IP address fields in configuration file should accept mask
103 format as well, IP/MASK, and not just plain IP.
105 o Connection classes should be actually implemented in
106 serverconfig.c. They can be defined but they are totally
107 ignored currently. And they should be redefined also.
110 TODO/bugs In SILC Libraries
111 ===========================
113 o WIN32 silc_net_create_connection_async does not work the same way
114 than on Unix. Do it with threads on WIN32. The function works but
115 is not actually async currently.
121 o Compression routines are missing. The protocol supports packet
122 compression thus it must be implemented. SILC Zip API must be
123 defined. zlib package is already included into the lib dir (in CVS,
124 not in distribution), but it is not used yet, and it requires some
125 tweaking on the Makefiles (we want static lib not shared).
127 o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
128 SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
131 o X.509 certificate support. SILC protocol supports certificates and
132 it would be great to have support for them. This is a big task as
133 support has to be made for ASN.1 as well. I've looked into OpenSSL
134 package as it has X.509 certificate support (and ASN.1 as well).
135 The code does not look very good to my eye but it has some potentials.
136 This should be looked at more closely.
138 Naturally own SILC Certificate API has to be defined regardles what
139 the actual X.509 library is (OpenSSL X.509 or something else). Other
140 choice is to write own X.509 library but I'm not going to do it -
141 I can help to migrate the OpenSSL X.509 into SILC and I can help if
142 someone would like to write the X.509 library - but I'm not going
143 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
146 Other package that should be checked is the NSS's X509 library.
148 o SSH2 public keys support. Maybe - not really needed but could be
149 nice as SSH is widely used all over the place. SILC Protocol
150 supports SSH2 public keys.
152 o OpenPGP certificate support.
154 o Cipher optimizations (asm, that this) at least for i386 would be nice.