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 XXXXXXXXX cannot join +a channel from other servers
46 o Implement the <founder auth> and founder privileges gaining to
47 the JOIN command. This will bypass invite-only mode as well for
48 the client who got the founder mode during JOIN.
50 o Optimize the WHOIS and IDENTIFY commands to check if the request
51 includes an ID or multiple IDs, then they are checked from local cache
52 first, and not sent directly to router. This is because if they
53 are found in the local cache there's no need to send them to the
54 router. Only if some ID is not found, or an found entry is
55 incomplete it can be queried from the router. This way these
56 commands become faster, and for example JOIN command becomes a lot
57 faster since the server ends up resolving the same information only
58 once, as opposed to resolve it everytime JOIN command is issued, like
61 The same thing can be done with WHOWAS command as well.
63 It is important to send these requests to router only if they can be
64 expanded to many results (as when doing WHOIS for nickname). If
65 they are explicit (like requesting by ID) the local cache MUST be
66 searched before sending it to router.
68 o Announcements are incomplete: channel topics are not announced,
69 user modes (UMODE) are not announced.
71 o Change the server to connect to another server from low ports (706)
72 and not from high ports. Currently we cannot do incoming connection
73 checking by remote port because the port is not fixed.
75 o Backup router related issues
77 o After backup resume protocol the TOPIC_SET was not handled
78 correctly by all (unknown Channel ID).
80 o Channel user mode changes are notified unnecessarely when
81 switching to backup router on router crash.
83 o If client's public key is saved in the server (and doing public key
84 authentication) then the hostname and the username information could
85 be taken from the public key. Should be a configuration option!
87 o Add a timeout to handling incoming JOIN commands. It should be
88 enforced that JOIN command is executed only once in a second or two
89 seconds. Now it is possible to accept n incoming JOIN commands
90 and process them without any timeouts. THis must be employed because
91 each JOIN command will create and distribute the new channel key
92 to everybody on the channel.
94 o New configuration file format must be added. The new one will be
95 done using the dotconf config library (lib/dotconf). The following
96 tasks relates closely to this as well and must be done at the same time
97 when adding the new config file format:
99 o Server says that it is able to listen on multiple ports but
100 currently that is bogus. It can, but internals are for single
103 o Protocol execution timeouts are hard coded, should be
106 o IP address fields in configuration file should accept mask
107 format as well, IP/MASK, and not just plain IP.
109 o Connection classes should be actually implemented in
110 serverconfig.c. They can be defined but they are totally
111 ignored currently. And they should be redefined also.
114 TODO/bugs In SILC Libraries
115 ===========================
117 o WIN32 silc_net_create_connection_async does not work the same way
118 than on Unix. Do it with threads on WIN32. The function works but
119 is not actually async currently.
125 o Compression routines are missing. The protocol supports packet
126 compression thus it must be implemented. SILC Zip API must be
127 defined. zlib package is already included into the lib dir (in CVS,
128 not in distribution), but it is not used yet, and it requires some
129 tweaking on the Makefiles (we want static lib not shared).
131 o Implement the defined SilcDH API. The definition is in
132 lib/silccrypt/silcdh.h.
134 o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
135 SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
138 o X.509 certificate support. SILC protocol supports certificates and
139 it would be great to have support for them. This is a big task as
140 support has to be made for ASN.1 as well. I've looked into OpenSSL
141 package as it has X.509 certificate support (and ASN.1 as well).
142 The code does not look very good to my eye but it has some potentials.
143 This should be looked at more closely.
145 Naturally own SILC Certificate API has to be defined regardles what
146 the actual X.509 library is (OpenSSL X.509 or something else). Other
147 choice is to write own X.509 library but I'm not going to do it -
148 I can help to migrate the OpenSSL X.509 into SILC and I can help if
149 someone would like to write the X.509 library - but I'm not going
150 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
153 Other package that should be checked is the NSS's X509 library,
154 which I like more over OpenSSL package.
156 o SSH2 public keys support.
158 o OpenPGP certificate support.
160 o Cipher optimizations (asm, that this) at least for i386 would be nice.