updates.

[silc.git] / TODO

diff --git a/TODO b/TODO
index 2994a564fdc3bb6ec9dbc92e5e84c9540c2a46fb..ea32c29409c4f2e575eee7081f690a347834a4be 100644 (file)
--- a/TODO
+++ b/TODO
@@ -25,12 +25,9 @@ TODO General
 TODO In SILC Client Library
 ===========================
 
- o TODO in commands (silc/local_command.c, lib/silcclient/command.c and
+ o TODO in commands (lib/silcclient/command.c and
                     silc/silclient/command_reply.c):
 
-       o Local command to handle private message keys is not done
-       o Local command to handle channel private keys is not done
-       o Local command to handle key agreement protocol is not done
        o RESTART command is not implemented
 
  o Client library crashes if for example server timeouts protocol
@@ -78,6 +75,13 @@ TODO In SILC Server
          When implementing this check that all commands handle the
          situation correctly when it is called as pending command
          (it should most likely check that cmd->pending == TRUE/FALSE).
+       o WHOIS and IDENTIFY command reply sending is buggy because
+         it may put status to be SILC_STATUS_LIST_START even though
+         there is only one valid entry (thus should be SILC_STATUS_OK).
+         This happens because it does not check the data.registered == FALSE
+         clients before setting the status.  Good fix for this would be
+         to make sure that the clients table does not include any
+         unregistered clients in the first place.
 
  o TODO in notify types (packet_receive.c):
 
@@ -169,18 +173,6 @@ TODO in the protocol before SILC 0.x
          passphrase or public key that can be used in the authentication
          when regaining the founder rights.
 
- o New packets and features in the packets
-   (draft-riikonen-silc-pp-xx.txt):
-
-       o Define the Private Message packet to include private message
-         flags and define the flags.  The flags could indicate whether
-         the message is, for example autoreply or the receiver should not
-         reply to the private messages.  What other flags?
-       o Define the Channel Message packet to include channel message
-         flags and define the flags.  Actually the flags should be same
-         as for the private message flags.  This way we can implement
-         for example the CTCP style ACTION (/ME command) messages.
-
  o New features in the KE/auth protocol
    (draft-riikonen-silc-ke-auth-xx.txt):