updates

[silc.git] / TODO

diff --git a/TODO b/TODO
index 21c58b76c80cb5ab32c2cc18298d81528a22c01c..52f0769d1ccb21d91954e5ea2b4646d67d6d5838 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,6 +1,8 @@
 TODO/bugs in Irssi SILC client
 ==============================
 
+ o /USERS does not show the user modes on the channel correctly.
+
  o Fix the silc_channels_join to parse the command like, with fe.
    silc_parse_command_line, because currently it ignores all options,
    including passphrase which makes autojoin impossible to +a channels.
@@ -11,6 +13,8 @@ TODO/bugs in Irssi SILC client
    keys is not possible because changing the key is not possible by the
    user.
 
+ o Add the server/router operator info to the statusbar.
+
  o /cumode for unknown nick does not give any error message.
 
 
@@ -37,6 +41,9 @@ TODO/bugs In SILC Server
 
  o Configuration file additions:
 
+       o Add version handling, to allow, disallow certain versions to
+         connect.
+
        o Add incoming connection frequency, incoming connection frequency
          for single IP address, key exchange frequency, key exchange
          frequency for single IP. Add also frequency base.
@@ -76,6 +83,8 @@ TODO/bugs In SILC Server
 TODO/bugs In SILC Libraries
 ===========================
 
+ o Fix possible buffer overflows in silc_id_render function.
+
  o WIN32 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.
@@ -86,6 +95,11 @@ TODO/bugs In SILC Libraries
  o SILC RNG does not implement random seed files, and they should be
    implemented.
 
+ o The SilcSocketConnection in the SFTP interface is actually redundant
+   and should perhaps be removed.  The application can save it in the
+   context it provides, which is delivered by SFTP libary to all 
+   callback functions.
+
 
 TODO in Toolkit Documentation
 =============================
@@ -100,11 +114,7 @@ Manual.
    Toolkit, how the build system works, where is everything, how
    new (external) projects can be glued into Toolkit (use irssi as an
    example), and how external projects can use Toolkit without gluing into
-   it (how to link etc).
-
- o Write "Programming conventions" document to describe the coding
-   and naming conventions used in the Toolkit (should not be 
-   actually the CodingStyle document, but something more general).
+   it (how to link etc), debugging, architecture, types, etc.
 
  o Write "Platform Implementations" document to describe what platforms
    Toolkit support, what has been implemented, what has not been, what