TODO/bugs in Irssi SILC client
==============================
- o Do not let irssi update the status bar on JOIN until the join command
- is successful, so that it does not update that I'm on the channel
- even though I could not join the channel.
+ o Add local command to switch the channel's private key when channel has
+ several private keys. Currently sending channel messages with many
+ keys is not possible because changing the key is not possible by the
+ user.
- o The CMODE notify handling in client library may return NULL
- client entry pointer to the application (when server was the CMODE's
- executor). Fix this somehow.
-
- o Add PERL scripting support from Irssi CVS.
+ o JOINing to +a (requires passphrase to JOIN) does not work on autojoin.
+ Seems the passwords in the .silc/config has no effect.
o Add local commands to list the current server and client public keys
that the user has. And a local command to dump the contents of the
public key to the screen. Something like LISTKEYS, SHOWKEY...
+ o The QUIT command should wait for server's disconnection (at least for
+ a while) before exiting the application.
+
+ o The JOIN command's HELP is generated from Irssi IRCs JOIN help and
+ the syntax is not same in SILC. This must be fixed. Most likely
+ we must forget the Irssi's JOIN command and mimic it to get our
+ required syntax for it too.
+
o We should get rid of the clientconfig.[ch] in Irssi SILC and move the
cipher, hash, hmac and pkcs configuration to the Irssi SILC's config
file.
+ o Add PERL scripting support from Irssi CVS.
+
o Extend the /HELP command to support sub commands or something. So
that user can say /help set mutual_authentication they would get
help of the mutual_authentication setting.
TODO/bugs In SILC Client Library
================================
- o Library should save the cumode and not start from 0 everytime then
- CUMODE is issued. A mechanism of getting the channel entry for
- CMODE and CUMODE by the command reply identifier must be added.
- Otherwise saving the modes for the channels and channel user
- entries are impossible since server does not send Channel ID as
- command reply in these commands.
-
- o All protocol execution timeouts are hard coded. They should be
- configurable and the Irssi SILC client should be able to set them
- with for example /set key_exchange_timeout etc. The silc_client_alloc
- should take a Params structure or something as argument.
-
- o silc_client_close_connection leaks memory. Read the XXX from code.
-
- o The client library must manage somehow when receiving client that has
- same nickname, same server, same username but different Client ID than
- what we have in the cache. It is now assumed that they are different
- client but it might not be. It should at least number the clients
- using the client->num so that they can be accessed from the user
- interface separately or it could just remove the old client unless
- it is on some channels.
+ o JOIN command's argument handling is buggy. See the XXX in the code.
TODO/bugs In SILC Server
========================
+ o On normal server the channel count can go negative (like -3 channels).
+
+ o Change the sever to connect to another server from low ports (706)
+ and not from high ports. Currently we cannot do incoming connection
+ checking by remote port because the port is not fixed.
+
+ o Add a timeout to handling incoming JOIN commands. It should be
+ enforced that JOIN command is executed only once in a second or two
+ seconds. Now it is possible to accept n incoming JOIN commands
+ and process them without any timeouts. THis must be employed because
+ each JOIN command will create and distribute the new channel key
+ to everybody on the channel.
+
+ o Optimize the JOIN command in normal server. When router returns
+ command reply for JOIN it returns the new channel key. We however
+ still create new channel key when processing the pending JOIN command.
+ This works ok but is not necessary.
+
+ o Optimize the WHOIS and IDENTIFY commands to somehow check whether the
+ requested clients are on some channel that the server knows about. If
+ this is the case then the request is not needed to be forwarded to the
+ router. One specific optimization could be done with JOIN command.
+ If the previous command to the WHOIS and IDENTIFY commands are JOIN
+ command (from the client) it can be expected (though it must be
+ verified) that the client is resolving the users on the channel it just
+ joined. If server has done this once there is really no reason to
+ resolve it twice (from the router), it can reply directly back with
+ the information it knows. This is because the server would (will)
+ receive notifications from the router for users that are on a local
+ channel.
+
+ The same is with whowas command. Actually with all these commands
+ it should be checked also whether the requested information is local.
+ If it is, there is no reason to send it to the router, since the server
+ knows it best.
+
+ o Add support for sending the LIST command to primary router on normal
+ server to receive all the created channels. Currently the command
+ returns only the channels the server knows about. The protocol spec
+ does not prohibit of sending the LIST to the router.
+
o Incomplete IPv6 support:
o silcd/serverid.c and its routines supports only IPv4.
- o DNS/IP lookup blocks the server. This must be fixed. Check the
- resolver stuff (resolver(3), resolver(5)). Either we have to do the
- own resolver stuff (through scheduler, if possible without writing
- too much own stuff) or use threads.
-
- o The backup router support described in the protocol specification
- should be done at some point.
+ o Add perhaps /var/run/silcd.pid for PID information for the server.
o New configuration file format must be added. The new one will be
done using the dotconf config library (lib/dotconf). The following
TODO/bugs In SILC Libraries
===========================
- o Incomplete IPv6 support:
-
- o All network routines in lib/silcutil/silcnet.[ch] does not
- support IPv6.
- o silc_id_render supports only IPv4 based ID's in the file
- lib/silcutil/silcutil.c.
+ o Security fixes from the latest draft for MAC key and MAC computation:
+ the packet sequence number.
o Compression routines are missing. The protocol supports packet
compression thus it must be implemented. SILC Comp API must be
and uint32 as data and data length as arguments. Now some of the
routines do already that but most of the routines use SilcBuffer.
The SilcBuffer ones should be removed since buf->data and buf->len
- is more convenient to use. However, the silc_buffer_[un]format
- routines support only SilcBuffer so they would require reallocation
- of SilcBuffer. Maybe support for raw data (and not just SilcBuffer)
- should be added silc_buffer_[un]format_? routines. These are currently
- only cosmetic changes but at some point must be done to make the
- payload interfaces consistent.
+ is more convenient to use. These are currently only cosmetic changes
+ but at some point must be done to make the payload interfaces
+ consistent.
+
+ o Incomplete IPv6 support:
+
+ o All network routines in lib/silcutil/silcnet.[ch] does not
+ support IPv6.
+ o silc_id_render supports only IPv4 based ID's in the file
+ lib/silcutil/silcutil.c.
o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
in separately.
+TODO/Bugs in native WIN32 support (libraries)
+=============================================
+
+ o silc_net_create_connection_async does not work the same way than on
+ Unix. Do it with threads on WIN32. The function works but is not
+ actually async currently.
+
+
TODO In SILC Protocol
=====================
TODO After 1.0
==============
- o Pthreads support. A lot of problems are solved with server (and with
- client as well) if we add pthread support. We can forget things such
- as non-blocking connecting etc, and we can do things such as DNS/IP
- lookups async. The server itself also benefits great deal from
- threads, especially from performance point of view.
-
- But, this is not a small task and almost entire SILC Library has to
- be made re-entrant. Own API is probably added for the threads support
- to make changes in the future as painless as possible. So the API
- would have things like silc_mutex_lock, silc_mutex_unlock and
- friends...
-
o X.509 certificate support. SILC protocol supports certificates and
it would be great to have support for them. This is a big task as
support has to be made for ASN.1 as well. I've looked into OpenSSL
projects / silc.git / blobdiff